Fixes are available
APAR status
Closed as program error.
Error description
In IBM Business Process Manager V8.0.1.2 or V8.5.0.1, if WebSphere Application Server runtime provisioning is enabled, users receive an HTTP 500 error ("Error 500: java.lang.NullPointerException" is displayed in the browser) when they log in to Process Center, Process Portal, and the Process Admin Console. Additionally, a NullPointerException and the following stack trace are written to the SystemOut.log file on the server or cluster where the corresponding application is deployed: [12/19/13 14:26:09:625 EST] 0000006e ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: An exception was thrown by one of the service methods of the servlet [/jsp/index.jsp] in application [IBM_BPM_Portal_MINZHAOVMTORNode04_server1]. Exception created : [java.lang.NullPointerException at com.lombardisoftware.portal.utils.ContextRootUtils.getAllContext Roots(ContextRootUtils.java:15) at com.ibm._jsp._index._jspService(_index.java:261) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1230) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:779) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:478) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest (ServletWrapperImpl.java:178) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleR equest(GenericServletWrapper.java:122) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrappe r.handleRequest(AbstractJSPExtensionServletWrapper.java:205) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(We bAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterChain.java:97) at com.ibm.bpm.social.servlet.filters.CachingFilter.doFilter(Cachin gFilter.java:69) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi lterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterChain.java:91) . . .
Local fix
Disable runtime provisioning (uncheck "Start components as needed" in the WebSphere administrative console), as described in more detail at: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ com.ibm.websphere.express.doc/info/exp/ae/urun_rappsvr.html
Problem summary
**************************************************************** * USERS AFFECTED: IBM BPM V8.5 Advanced, Standard, and * * Express * **************************************************************** * PROBLEM DESCRIPTION: In the IBM BPM V8.0.1.2 fix pack, the * * Process Center, Process Portal, and * * Process Admin Console components * * depend on the Context Root Service of * * Business Process Manager, which is a * * new runtime component, and this * * component does not start * * automatically when the runtime * * provisioning feature is enabled for * * the WebSphere Application Server. * * Therefore, when you log in to Process * * Center, Process Portal or Process * * Admin Console, you might encounter * * problems and a NullPointerException * * might be logged in the SystemOut.log * * file on the server or cluster where * * the corresponding application is * * deployed. * * Runtime provisioning is not supported * * for IBM BPM, but the Context Root * * Service should always start * * regardless of whether provisioning is * * enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the Start components as needed option is enabled in the administrative console, you might encounter problems logging into Process Center, Process Portal, or Process Admin Console.
Problem conclusion
When the fix is applied, the metadata that is associated with the context root configuration component is modified so that it starts automatically, even if the runtime provisioning feature of the application server is enabled. To get the fix, go to Fix Central (http://www.ibm.com/support/fixcentral) and search for JR48515: 1. Select the product group, product, installed version, and platform, click Continue. 2. Select APAR or SPR, enter JR48515, and click Continue. When downloading fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Temporary fix
Yes. In the administrative console: select Application servers > ServerName page[server1] and clear the Start components as needed option.
Comments
APAR Information
APAR number
JR48515
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-14
Closed date
2013-12-19
Last modified date
2014-01-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021