PM44556: SERVER STARTUP IS SLOWED BY CODED WHICH REDUNDANTLY OPENS AN EARFILE WHEN OBTAINING MODULE CLASS PATHS.

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Server startup slowed by redundant openEARFile from
  getLibraryDirectoryClassPath
  
  The problem is exposed specifically in the Feature Pack for
  EJB 3.0 for IBM WebSphere Application Server, when moving to
  version 6.1.0.37 of the application server.
  
  
  [7/26/11 22:19:08:484 EDT] 0000002a wtp           2
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl openSpecificArchive Stack trace of
  openSpecificArchive caller:
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.util.ArchiveUtil
  .dumpStackTrace(ArchiveUtil.java)
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.logArchiveCharacteristics(CommonarchiveFactoryImpl
  .java)
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.openSpecificArchive(CommonarchiveFactoryImpl.java)
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.openEARFile(CommonarchiveFactoryImpl.java)
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl
  .getLibraryDirectoryClassPath(ArchiveImpl.java)
  
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl
  .getDependencyClassPath(ArchiveImpl.java)
  
  com.ibm.ws.classloader.ClassGraph.addModule(ClassGraph.java:202)
  
  com.ibm.ws.classloader.ClassLoaderManager.initialize(ClassLoader
  Manager.java:213)
  
  com.ibm.ws.classloader.ClassLoaderManager.<init>(ClassLoaderMana
  ger.java:176)
  
  com.ibm.ws.runtime.component.DeployedApplicationImpl.start(Deplo
  yedApplicationImpl.java:776)
  
  com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication
  (ApplicationMgrImpl.java:945)
  
  com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.r
  un(ApplicationMgrImpl.java:2120)
  
  com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializ
  er.run(WsComponentImpl.java:342)
  com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1551)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application server startup is slowed    *
  *                      by a rendundant calls to open           *
  *                      Enterprise Application Archive files    *
  *                      (EAR files).                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During application server startup, deployed enterprise
  applications are started.  That requires processing of the
  underlying enterprise application archive files (EAR files).
  A step of the processing of those enterprise application
  archives files performs a redundant open step, severely
  impacting startup performance.
  No program error occurs.  This problem manifests as a
  performance degradation.
  The problem signature is visible in the trace output for trace
  specification com.ibm.config.eclipse.wtp=FINER, with a showing
  of the following stack trace:
  [7/26/11 22:19:08:484 EDT] 0000002a wtp           2
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl openSpecificArchive Stack trace of
  openSpecificArchive caller:
  org.eclipse.jst.j2ee.commonarchivecore.internal.util.ArchiveUtil
  .dumpStackTrace(ArchiveUtil.java)
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.logArchiveCharacteristics(CommonarchiveFactoryImpl
  .java)
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.openSpecificArchive(CommonarchiveFactoryImpl.java)
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.Commonarchi
  veFactoryImpl.openEARFile(CommonarchiveFactoryImpl.java)
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl
  .getLibraryDirectoryClassPath(ArchiveImpl.java)
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl
  .getDependencyClassPath(ArchiveImpl.java)
  com.ibm.ws.classloader.ClassGraph.addModule(ClassGraph.java:202)
  com.ibm.ws.classloader.ClassLoaderManager.initialize(ClassLoader
  Manager.java:213)
  com.ibm.ws.classloader.ClassLoaderManager.<init>(ClassLoaderMana
  ger.java:176)
  com.ibm.ws.runtime.component.DeployedApplicationImpl.start(Deplo
  yedApplicationImpl.java:776)
  com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication
  (ApplicationMgrImpl.java:945)
  com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.r
  un(ApplicationMgrImpl.java:2120)
  com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializ
  er.run(WsComponentImpl.java:342)
  com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1551)
  

Problem conclusion

• The problem is exposed specifically in the Feature Pack for
  EJB 3.0 for IBM WebSphere Application Server, when moving to
  version 6.1.0.37 of the application server.
  
  The problem only occurs in the Feature Pack for EJB 3.0. This
  problem does not occur in any IBM WebSphere Application Server
  installation, version 6.1, that does not include the Feature
  Pack for EJB 3.0.  The problem is fixed in all versions of the
  IBM WebSphere Application Server version 7.0 and higher.
  
  The fix for this APAR is currently targeted for inclusion in
  the Feature Pack for EJB 3.0 for IBM WebSphere Application
  Server v6.1.0.41.  Please refer to the Recommended Updatespage
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP