Fixes are available
PI85587:java.lang.nullpointerexception when starting an eba containing an ejb
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
During startup, application fails with WSVR0067E: EJB container caught java.lang.NoClassDefFoundError: com.ibm.websphere.models.extensions.helpers.impl.PMEEJBJarExtens ionHelperImpl (initialization failure) with linked exception of Caused by: java.lang.NullPointerException at m.ibm.websphere.models.extensions.pmeext.commonext.serialization .DocumentRootUtil.createDocumentRootEClass(DocumentRootUtil.java : 60)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of OSGi * * applications. * **************************************************************** * PROBLEM DESCRIPTION: An EBA containing an EJB fails to * * start. A WSVR0067E message indicates * * NoClassDefFoundError caused by * * NullPointerException. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an Eclipse Modelling Framework (EMF) package is initialized, it is registered with the package registry associated with the thread's context class loader. When the EJB Container is first used it attempts to read its configuration data from the package registry. If the first application that uses the EJB Container is an OSGi application then the application startup will fail due to a failure while accessing the EJB Container's configuration stored in the package registry. The failure occurs because the context class loader set for the thread performing the start of the EJB Container for an OSGi application has been set to a classloader that is both different from, and not a parent of, the classloader that was used when the package was initially registered resulting in the EJB Container being unable to locate its required configuration.
Problem conclusion
The OSGi container was modifed so that the correct classloader was set as the thread's context class loader while starting the EJB Container during OSGi application startup. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.13 and 9.0.0.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Application startup order can be modified so that EJB Container initialization occurs during the startup of a non-OSGi application.
Comments
APAR Information
APAR number
PI85587
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-08-07
Closed date
2017-09-18
Last modified date
2017-09-18
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022