PH47514: IIOP REQUEST SHOULD BE PROHIBITED IF THE TRANSACTION CONTEXT HAS ALREADY TIMED OUT IN A SUBORDINATE

APAR status

• Closed as program error.

Error description

• An IIOP request made under a transaction context results in an
  org.omg.CORBA.TRANSACTION_ROLLEDBACK Exception with detail
  message "Duplicate registration attempted" after the 'Client
  Inactivity Timeout' for the transaction occurs on a downstream
  application server.
  
  An event message "Duplicate registration attempted" is written
  to the logs if event logging is enabled.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: TRANSACTION_ROLLEDBACK Exception        *
  *                      "Duplicate registration attempted"      *
  *                      occurs after a subordinate client       *
  *                      inactivity timeout.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a subordinate transaction branch's "Client Inactivity
  Timeout" occurs and the same transaction is then propagated
  back to the subordinate it will attempt to reregister with the
  superior coordinator.
  The duplicate registration will be detected by the superior
  coordinator, resulting in the request failing with an
  org.omg.CORBA.TRANSACTION_ROLLEDBACK Exception
  with detail message "Duplicate registration attempted".
  If event logging is enabled, the superior will generate a
  log entry "Duplicate registration attempted. Throw rollback
  exception".
  If the transaction timeout had occurred in the process
  making the IIOP request, existing behaviour would prohibit the
  request from being made, raising an
  org.omg.CORBA.TRANSACTION_ROLLEDBACK Exception with an empty
  detail message.  There would be no duplicate registration.
  The transaction service should prohibit the IIOP request when
  it has been informed that any of the current transaction's
  subordinate branches have timed out and exhibit the same
  behaviour that it would when the current transaction's
  local branch has timed out.  This would prevent both
  unnecessary work from being processed in the subordinate and
  the duplicate registration from occurring.
  

Problem conclusion

• The transaction service's client IIOP interceptor was modified
  so that it prohibits requests for which the current transaction
  context has timed out in a subordinate, the behaviour now
  matching that when the transaction has been timed out in the
  local process.
  
  The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.23 and 9.0.5.14. 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