PH28619: JTA COMMIT PRIORITY NOT APPLIED TO MQ PROVIDER JMS XARESOURCES

APAR status

• Closed as program error.

Error description

• An application read messages from queue manger QM1 and put
  messages to queue manager QM2. The desired behaviour was that
  messages would be put to QM2 before the message was removed
  from QM1.  Specifying the commit-priority on the resource-ref
  for the connection factory had no effect on the ordering of
  the XAResource.commit invocations.  The commit-priority
  worked as expected for resource-refs for JDBC datasources.
  

Local fix

• Possible workaround the issue by modifying the JDBC
  resource-refs commitPriority
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of JMS   *
  *                  using the WebSphere MQ Resource Adapter.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the WebSphere MQ JMS         *
  *                      provider in a JTA transaction the       *
  *                      commit-priority set on the              *
  *                      resource-ref has no effect.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The extended bindings for an application's resource references
  can be used to specify a commit-priority to control the order
  in which different XAResources enlisted with a JTA
  transaction are committed.  Although tooling allows the
  commit-priority to be set for all resource-ref types it was
  never applied to JMS Connection Factories (and is not
  relevant for JMS Queues or Topics).  This is because in JMS,
  work is associated with the JMS Session, not the JMS
  Connection associated with the resource-ref.
  

Problem conclusion

• The Messaging and J2C components were modified to allow the
  commit-priority specified for the resource-ref of a JMS
  Connection Factory (and Queue/Topic sub-types), bound to a
  WebSphere MQ JMS Provider, to be applied to the XAResources
  associated with the work performed under the JMS Sessions
  created from the JMS Connection Factories.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.19 and 9.0.5.7. 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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP