12.2 WorkflowUsers Are Unable To Open Notification Summary For Other Users Due To Error 'You have encountered an unexpected error. Please contact the system administrator for assistance' And 'OAException: Could not load application module NotificationsAM' (Doc ID 2290956.1)

Last updated on AUGUST 04, 2017

Applies to:

Oracle Workflow - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

E-Business Suite 12.2 Workflow, Workflow Administration Worklist related issues

 


Users report when they click on the Notification Summary for a specific user the following error is received:

Error: You have encountered an unexpected error. Please contact the system administrator for assistance.

The error stack for the above message contains the following:

Error Page
Exception Details.
oracle.apps.fnd.framework.OAException: Could not load application module
'oracle.apps.fnd.wf.worklist.server.NotificationsAM'.
at
oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicatio
nRegistry.java:279)
at
oracle.apps.fnd.framework.webui.OAJSPApplicationRegistry.registerApplicationModule(OAJSPApplicatio
nRegistry.java:78)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1348)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:582)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:470)
at _pages.__oa._jspService(__oa.java:233)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
at
weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:159)
at _pages.__rf._jspService(__rf.java:239)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.apps.fnd.security.WLFilter.doFilter(WLFilter.java:213)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.apps.jtf.cabo.interceptor.JTFWrapperFilter.doFilter(JTFWrapperFilter.java:149)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:432)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(AccessController.java:366)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:60)


The issue can be reproduced at will with the following steps:

1. Click on the Notification Summary for a specific user.

2. Confirm the above error is received.

The issue has the following business impact:

Due to this issue, cannot click on the Notification Summary for a specific user.

Changes

 GST patches were applied.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms