PM74554: REDUCE STARTUP TIME FOR APPLICATIONS WITH EJB MODULES THAT USE A NNOTATIONS.

7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• EJB modules that use annotations do not cache annotations data
  for the EJB descriptor.  Repeat scanning for annotations slows
  application startup.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0 with EJB modules that use       *
  *                  annotations.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Annotations data for EJB modules which  *
  *                      use annotations is not cached.          *
  *                      Recomputing this data slows             *
  *                      application startup.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Annotations data for EJB modules is recomputed every time the
  application is visited.  Recomputing this data requires a scan
  of the classes of the EJB modules and includes an extensive
  process to merge the annotations data with data from the EJB
  module deployment descriptors. Caching the EJB annotations
  data avoids the extensive scan and merge processing.
  

Problem conclusion

• Code updates were made to cause annotations data for EJB
  modules to be written to the file "ejb-jar_merged.xml", which
  is saved when the application is deployed to the application
  server.  Subsequent reads of the application data read the
  cached data instead of recomputing this data.  A read of the
  application data occurs during application startup.
  
  For an application which contains a majority of content as EJB
  modules which are enabled to use annotations, the use of the
  cached data can result in an up to 40% reduction in
  application startup time.
  
  The updates for this APAR are a backport of changes introduced
  to the IBM WebSphere Application Server v8.0.  The updates are
  not applicable for the IBM WebSphere Application Server v6.1.
  
  Enablement of the updates require setting a java custom
  property.  To enable this update, set the custom
  property "org.eclipse.jst.j2ee.commonarchivecore.enable.ejb.desc
  riptor.cache" to "true".
  
  When enabled, this update changes the file
  "META-INF/ejb-jar_merged.xml", which is written during
  application deployments, from being only for debugging
  purposes to being an active file.  With this update enabled,
  "META-INF/ejb-jar_merged.xml" must be retained to keep the
  performance improvement, and should not be edited.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.27.  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 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 EXPRESS

• Fixed component ID

  5724I6300

Applicable component levels

• R700 PSY

     UP