IZ73493: THE INCLUSION OF THE APACHE COMMONS-LOGGING JAR IN WSRR MAY CAUSE A CONFLICT WITH OTHER WEBSPHERE PRODUCTS.

APAR status

• Closed as program error.

Error description

• The issue is the difference in the Thread Context Class
  Loader.  If Thread Context ClassLoader is not set to
  WSRR, then when WSRR calls commons logging to load a
  logger, a Logger from WAS will be loaded.  This is a problem
  since the
  WSRR has already loaded commons logging classes and now there is
  Log class from two classloaders causing a conflict.
  (WSRR and WAS).
  

Local fix

• NA
  

Problem summary

• When WSRR is co-existing with other applications or products
  within WebSphere Application Server, the following error might
  occur:
  
  GSR5000I: Captured exception [1067]:
  org.apache.commons.logging.LogConfigurationException: Invalid
  class loader hierarchy. You have more than one version of
  'org.apache.commons.logging.Log' visible, which is not allowed.
  

Problem conclusion

• WSRR has now been rebuilt so that it no longer includes the
  commons-logging JAR. This will prevent the class loader error.
  
  This fix is targeted for inclusion in fix pack 3 for WSRR v6.3.
  

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

  SERVICE REGISTR

• Fixed component ID

  5724N7200

Applicable component levels

• R630 PSY

     UP

• R700 PSY

     UP