Under Siebel 8.1.1.5 HTTP 500 errors may be seen in BI Publisher when the Siebel Security Model is enabled (Doc ID 1351849.1)

Last updated on JULY 20, 2016

Applies to:

Siebel Reports - Version 8.1.1.5 [21229] to 8.1.1.5 [21229] [Release V8]
Information in this document applies to any platform.

Symptoms

Following application of the Siebel 8.1.1.5 FixPack users running Siebel BI Publisher reporting integration may find that their BI Publisher Server reports HTTP 500 error messages.

The HTTP 500 error messages can be encountered when the Siebel Security Model is set and attempts are either made to access the Roles & Permissions tab when logged in as the SuperUser or when attempting to login to the BI Publisher console as a Siebel user.

Examination of the application.log file which can be found in the %ORAHOME%\oc4j_bi\j2ee\home\application-deployments\xmlpserver directory will show the following call stack :

11/08/24 07:55:24.640 xmlpserver: Servlet error
javax.xml.parsers.FactoryConfigurationError: Provider weblogic.xml.jaxp.RegistrySAXParserFactory could not be instantiated: java.lang.ClassCastException: com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:30)
at org.apache.axis.utils.XMLUtils.initSAXFactory(XMLUtils.java:209)
at org.apache.axis.utils.XMLUtils.<clinit>(XMLUtils.java:110)
at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:179)
at org.apache.axis.AxisEngine.init(AxisEngine.java:172)
at org.apache.axis.AxisEngine.<init>(AxisEngine.java:156)
at org.apache.axis.client.AxisClient.<init>(AxisClient.java:52)
at org.apache.axis.client.Service.getAxisClient(Service.java:104)
at org.apache.axis.client.Service.<init>(Service.java:113)
at com.siebel.apps.shared.xmlp.security.BIPSiebelSecurityWSLocator.<init>(BIPSiebelSecurityWSLocator.java:12)
at oracle.apps.xdo.security.SiebelValidator.<init>(SiebelValidator.java:84)
at oracle.apps.xdo.servlet.security.SecurityManagerImpl.getSiebelPrincipal(SecurityManagerImpl.java:1364)
at oracle.apps.xdo.servlet.security.SecurityManagerImpl.getPrincipal(SecurityManagerImpl.java:348)
at _login._jspService(_login.java:281)
at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.1.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:197)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.1.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)

Changes

The behaviour may occur after application of the Siebel 8.1.1.5 FixPack.

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