PM57523: EJB APPLICATION FAILS TO START DURING SERVER STARTUP WHEN CPU USAGE IS HIGH.

Fixes are available

APAR status

Closed as program error.

Error description

During server startup when there are several processes that
start along with applications, the CPU usage can increase.
When the CPU consumption is high, the following exception can be
seen in the logs and EJB applications can fail to start.
.
00000022 EJBMDOrchestr E  CNTR0149E: The start up process for
the myEJB.jar enterprise bean in the myEJBModule module failed
with the following exception:
java.lang.IllegalStateException: XMLResource is null
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.storeV
ersionID(EnterpriseBeanImpl.java:737)
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.storeV
ersionID(EnterpriseBeanImpl.java:747)
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.getVer
sionID(EnterpriseBeanImpl.java:755)
 at
com.ibm.ejs.models.base.extensions.ejbext.impl.EJBJarExtensionIm
pl.getEJBExtension(EJBJarExtensionImpl.java:432)
 at
com.ibm.ws.metadata.ejb.EJBMDOrchestrator.createBeanMetaData(EJB
MDOrchestrator.java:734)
 at
com.ibm.ws.metadata.ejb.EJBMDOrchestrator.processBean(EJBMDOrche
strator.java:1315)
 at
com.ibm.ws.runtime.component.EJBContainerImpl.startModule(EJBCon
tainerImpl.java:2618)

00000022 EJBContainerI E  WSVR0040E: addEjbModule failed for
myEJB.jar [class
com.ibm.ws.runtime.component.DeployedEJBModuleImpl]
com.ibm.ws.exception.RuntimeWarning:
java.lang.IllegalStateException: XMLResource is null
 at
com.ibm.ws.metadata.ejb.EJBMDOrchestrator.processBean(EJBMDOrche
strator.java:1390)

Caused by: java.lang.IllegalStateException: XMLResource is null
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.storeV
ersionID(EnterpriseBeanImpl.java:737)
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.storeV
ersionID(EnterpriseBeanImpl.java:747)
 at
org.eclipse.jst.j2ee.ejb.internal.impl.EnterpriseBeanImpl.getVer
sionID(EnterpriseBeanImpl.java:755)
 at
com.ibm.ejs.models.base.extensions.ejbext.impl.EJBJarExtensionIm
pl.getEJBExtension(EJBJarExtensionImpl.java:432)
 at
com.ibm.ws.metadata.ejb.EJBMDOrchestrator.createBeanMetaData(EJB
MDOrchestrator.java:734)
 at
com.ibm.ws.metadata.ejb.EJBMDOrchestrator.processBean(EJBMDOrche
strator.java:1315)
 ... 15 more

Local fix

Try to lower the number of processes that startup simultaneously
so that CPU usage does not increase. Then applications can
startup successfully.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  with very large, slow-starting              *
*                  applications                                *
****************************************************************
* PROBLEM DESCRIPTION: Exceptions reading metadata can occur   *
*                      for applications that take a long       *
*                      time to start                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When module metadata is accessed, the module code holds the
documents open for some time, with an alarm set to close them.
In the case of a very slow-starting application, however, the
alarm could close the module before the startup process is
complete, resulting in an exception.

Problem conclusion

The alarm behavior was modified, with the documents no longer
being closed during application startup.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.4, and 8.5.0.1.  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
PM57523
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-06
Closed date
2012-05-14
Last modified date
2012-05-14

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

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM57523: EJB APPLICATION FAILS TO START DURING SERVER STARTUP WHEN CPU USAGE IS HIGH.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?