PH40106: WMQ ACTIVATION SPECIFICATION USES INCORRECT CLASSPATH FOR XA RECOVERY WHEN RESOURCE ADAPTER NATIVE LIBRARY PATH SPECIFIED

APAR status

• Closed as program error.

Error description

• The XA recovery process for WebSphere MQ Activation
  Specifications loads WebSphere MQ Java classes from the native
  library path specified on the WebSphere MQ Resource Provider
  instead of the relevant classes from the WebSphere MQ Resource
  Adapter.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of JMS   *
  *                  Provider WebSphere MQ using 'Bindings then  *
  *                  Client' transport                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect Classpath used on XA          *
  *                      Recovery for JMS Provider WebSphere     *
  *                      MQ when using 'Bindings then Client'    *
  *                      transport                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using JMS with WebSphere MQ as an XA Resource Manager in
  a JTA transaction and 'Bindings then Client' transport, the
  Classpath to be used on XARecovery that is written to the
  transaction service partner logs contains both the native
  library path for Bindings transport and the Java Classpath for
  the WMQ Resource Adapter for Client transport.  The native
  library path is prepended to the front of the XA Recovery
  Classpath for the WMQ XA Resource.
  The installation of WebSphere MQ containing the native
  libraries also includes the WMQ Client jar files and therefore,
  if XARecovery switches to Client transport then the WMQ Java
  Client classes from the WMQ installation will be used,
  instead of the Java classes from the WMQ Resource Adapter.
  This behaviour does not normally cause any functional issues
  but should be corrected.
  

Problem conclusion

• The Classpath information for WMQ XAResources using 'Bindings
  then Client' transport was modified so that if XARecovery
  processing fell back to Client transport then the correct
  classes from the WMQ Resource Adapter are used.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.21 and 9.0.5.10. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP