PH58504: PROVIDE MECHANISM TO SPECIFY JTA COMMITPRIORITY OF WSCOORDINATORS

APAR status

• Closed as program error.

Error description

• Provide a mechanism to specify the JTA commitPriority of
  WSCoordinators.  This will allow explicit control of the
  ordering with which 2PC flows (eg prepare and commit) are sent
  to subordinate transaction branches created by the propagation
  of transaction context via IIOP (ie on EJB requests), relative
  to other resources enlisted with the JTA transaction.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A a mechanism was required to specify   *
  *                      the JTA commitPriority of subordinate   *
  *                      transaction branches created via        *
  *                      JTS/IIOP.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A a mechanism was required to specify the JTA commitPriority
  of subordinate transaction branches created via JTS/IIOP.
  

Problem conclusion

• A mechanism was provided to allow explicit control of the
  ordering with which 2PC flows (eg prepare and commit) are sent
  to subordinate transaction branches created by the propagation
  of JTA transaction context via JTS/IIOP (ie on EJB requests),
  relative to other resources enlisted with the transaction,
  when a JTA transaction completes.
  
  The commitPriority used by an application server when flowing
  2PC to any of its JTS/IIOP subordinate transaction branches
  can be specified by setting the JVM System Property
  com.ibm.ws.tx.jta.WSCoordinatorPriority to an Integer value eg:
  
  com.ibm.ws.tx.jta.WSCoordinatorPriority=-1
  
  The default commitPriority is 0 and remains unchanged.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.25 and 9.0.5.19. 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