Fix (APAR): PI35502 Status: Fix Release: 8.5.5.5 Operating System: AIX,HP-UX,IBM i,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 257001 Date: 2015-03-12 Abstract: NullPointerException DURING LOOKUP OF A CONNECTIONFACTORY FROM A BPM-WXS ENVIRONMENT Description/symptom of problem: PI35502 resolves the following problem: ERROR DESCRIPTION: The lookup of a ConnectionFactory from a BPM-WXS environment may fail with the following error : com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NullPointerException] at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:1103) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup( Helpers.java:796) at com.ibm.ws.naming.jndicos.CNContextImpl.processBoundObjectForLoo kup(CNContextImpl.java:2877) at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CN ContextImpl.java:3974) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1876) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.j ava:1777) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl. java:1434) at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.jav a:616) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:165) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179) at javax.naming.InitialContext.lookup(InitialContext.java:436) at com.ibm.bpm.embeddedecm.EmbeddedECMTWTestCase.createJMSSession(E mbeddedECMTWTestCase.java:160) at com.ibm.bpm.embeddedecm.documents.DocumentPermissionsTest.testAc cessControlMigration(DocumentPermissionsTest.java:347) Caused by: java.lang.NullPointerException at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.createMCFandP M(ConnectionFactoryBuilderServerImpl.java:570) at com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl.processObject Instance(ConnectionFactoryBuilderServerImpl.java:1067) at com.ibm.ejs.j2c.ServerFunction.processObjectInstance(ServerFunct ion.java:1517) at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(C onnectionFactoryBuilderImpl.java:660) at javax.naming.spi.NamingManager.getObjectInstanceByFactoryInRefer ence(NamingManager.java:501) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.j ava:365) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE xt(Helpers.java:993) LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server V8.5 full profile PROBLEM DESCRIPTION: NullPointerException during lookup of a ConnectionFactory for a BPM-WXS environment RECOMMENDATION: None The lookup of a JMS connection factory can fail in a BPM-WXS (WebSphere Extreme Scale) environment involving the wsogclient.jar which is the eXtreme Scale client runtime for the WXS & BPM integration. The WebSphere J2C component is dependent on the the RAS component to determine whether the lookup is from a server or client. But WebSphere eXtreme Scale is using the RAS server function with the eXtreme Scale client runtime and this makes the J2C component take the server side code path instead of theclient side code path, resulting in the NullPointerException. PROBLEM CONCLUSION: The WebSphere J2C code has been updated to rely on the WebSphere runtime component to determine if it has to use the server code path or client code path. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Mark with an X the: 1) Release the fix applies to 2) The Editions that apply 3) And then DELETE THIS NOTE Fix applies to Editions: Release 8.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) __ Edge Components __ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required. The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before applying the iFixes. Restart WebSphere Application Server after applying the iFixes. Directions to remove fix: The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes. http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp. Shutdown WebSphere Application Server before removing the iFixes. Restart WebSphere Application Server after removing the iFixes. Directions to re-apply fix: 1) Shutdown WebSphere Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: