PM61787: LOADING SLF4J CLASSES USING -WSADMIN_CLASSPATH PARAMETER IS NOT WORKING IN V8 WITH WSADMIN.SH/BAT TOOL.

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Loading SLF4J classes (http://slf4j.org/) by adding the
  respective JARs to the wsadmin classpath works in WebSphere
  Application Server V6.1 and V7 but fails in WebSphere
  Application Server V8.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Attempts to load SLF4J classes          *
  *                      packaged in a resource provider or      *
  *                      added to the wsadmin classpath fails.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server V8.0 introduced the concept of
  "always protected" packages as a means of preventing
  application code from accessing packages that were intended to
  be internal to WebSphere Application Server (specifically
  SLF4J), with the filtering done by WebSphere Application
  Server's extension class loader.  However, since there are
  acceptable use cases for packaging user-provided classes in
  this class loader, this filtering prevented users from
  utilizing their own versions of these libraries as well.
  

Problem conclusion

• The package protection mechanism was changed to allow
  protected packages to be loaded from the Extension Class Loader.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 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 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

• R800 PSY

     UP

• R850 PSY

     UP