Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
A NullPointerException occurring when performing an InitialContextlookup operation: java.lang.NullPointerException at com.ibm.ws.eba.app.runtime.services.internal.JNDINestedFramework Support.augmentEnvironment (JNDINestedFrameworkSupport.java:69) at org.apache.aries.jndi.AugmenterInvokerImpl.augmentEnvironment(Au gmenterInvokerImpl.java:48) at org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitia lContext(OSGiInitialContextFactoryBuilder.java:42) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.j ava:695) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav a:318) at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContex t.java:346) at javax.naming.InitialContext.lookup(InitialContext.java:422)
Local fix
Not Applicable
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - JMX * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException during JNDI lookup * * from JMXConnectorFactory.connect * **************************************************************** * RECOMMENDATION: * **************************************************************** javax.management.remote.JMXConnectorFactory.connect causes a JNDI lookup to take place. This is intercepted by JNDI code that assumes an OSGi bundle context is available. In the JMX case, there is no context and so a NullPointerException occurs
Problem conclusion
The JNDI code has been updated to check for the existence of a bundle context before using it. 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
Temporary fix
Comments
APAR Information
APAR number
PI28223
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-22
Closed date
2015-04-22
Last modified date
2015-04-22
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
28 April 2022