OSM Orchestration UI Throws Error In Logs "javax.faces.FacesException: Broken pipe"
(Doc ID 1623389.1)
Last updated on MARCH 31, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.0 and laterInformation in this document applies to any platform.
**** Currency checked on 13-Oct-2017********
Symptoms
While opening Orchestration UI from Task management UI through URL link, OSM throws Error.
Ex - In task management UI, we leverage OSM-7 feature to link to the order to be opened in Orchestration UI. Example of the URL which gets displayed is as below - http://hostname/osmwebui/faces/orderDetails?OrderID=6200066&OrderHistID=0
When user clicks on the link from task management UI, it takes a long time to load. Then when it opens, it opens in a small portion of the page and also throws the error shown below.
Error or Warnings customer observes in their environment :
<WARN_NO_USERS_PATTERN oracle.security.idm.ObjectNotFoundException: No User found matching the criteria at oracle.security.idm.providers.stdldap.util.DirectSearchResponse.initSearch(DirectSearchResponse.java:174)
at oracle.security.idm.providers.stdldap.util.NonPagedSearchResponse.(NonPagedSearchResponse.java:52)
in phase RENDER_RESPONSE 6
javax.faces.FacesException: Broken pipe
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:804)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:294)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:214)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)
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:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
Environment details of Test:
My environment details :
1) WLS 10.3.5 .
2) OSM patch 7.2.0.7 and 7.2.0.6.2
3) JDK 64-Bit Architecture .
4) Single server and clustered with two managed Servers.
5) Standalone DB .
Customer environment :
1) WLS 10.3.5 .
2) OSM patch 7.2.0.6.2 .
3) JDK 64-Bit Architecture .
4) Clustered with 2 Managed Servers .
5) Has a Proxy Server or Load Balancer Configured .
6) Connects to a RAC DB & not a standalone DB .
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |