PI68791: NOCLASSDEFFOUNDERROR WHEN USING SHARED LIBRARY AND BLA.

8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• This problem was discovered only on WebSphere Application
  Server Network Deployment edition V8.5.5.9.  The same wsadmin
  scripting is used across all versions. The problem does not
  occur in any other versions we are running, including both
  V8.0.0.10 and V8.5.5.5. we are facing NoClassDefFoundError
  when the application tries to load classes from the shared
  library.
  

Local fix

• L3 recommended to the change to starting weight of the EAR to
  "2" while keeping the composition unit shared library
  dependency at the default "1"
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  utilizing Business Level Applications with  *
  *                  library assets                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A ClassNotFoundException occurs when    *
  *                      loading a class packaged in a library   *
  *                      asset associated with a Business        *
  *                      Level Application                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server starts the composition units
  (applications and assets) of Business Level Applications
  according to starting weight; items of equal starting weights
  are started in an undefined order, based on their presence in
  the configuration.  This, unfortunately, is not an appropriate
  behavior in the case of library assets, as application assets
  will likely depend on them (but not vice-versa).  When an
  application starts before a library of the same starting
  weight, it may fail to find classes packaged in that library.
  

Problem conclusion

• Library assets now start before application assets of the same
  starting weight.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.12.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Modifying the weight of the assets such that the application
  asset has a higher starting weight than the library asset will
  resolve the issue.
  

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

• R850 PSY

     UP