PM31170: BLA SHARED LIBRARY ASSETS CAN BE STARTED AFTER THE APP THAT DEPENDS ON IT AT SERVER STARTUP.

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
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

• A shared library that is imported as an asset to a business
  level application (BLA) is not created and associated until
  the composition unit is started when the BLA is started.
  It is possible that an enterprise application archive (EAR)
  may depend on that shared library, but because both the EAR
  and shared library have the same starting weight by default,
  the shared library may be started after the EAR has started.
  This means that the EAR cannot load classes from the shared
  library until the BLA is restarted.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When BLA shared libraries and EARs      *
  *                      have the same starting weight, it is    *
  *                      possible for the shared libraries to    *
  *                      be started and created after the EAR    *
  *                      application that depends on it.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The server runtime starts all BLA composition units with the
  same starting weight at the same time - regardless of declared
  dependencies between assets such as BLA EAR assets depending
  on BLA shared library assets.
  

Problem conclusion

• This APAR resolves this problem by starting BLA shared library
  assets before BLA EAR applications when both have the same
  starting weight.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.17.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP