PI09134: WS-AT incorrectly rolledback if requester and provider resides on same JVM, due to missing header tag in response

APAR status

• Closed as program error.

Error description

• WS-AT incorrectly rolledback when SOAPFault received if
  requester and provider reside on same JVM.
  By default, all SOAPFaults received by the WS-AT handlers at
  the client requester are delegated up to the application code
  to decide whether to mark the transaction as rollback only, or
  to continue with normal processing flow.
  However, if the WS-AT handlers at the client requester detects
  that there is evidence that the transactional integrity of the
  WS-AT flow has been compromised, the WS-AT handler itself will
  mark the transaction for rollback only. The handlers test for
  transactional integrity by checking for the presence of various
  header tags in the SOAP response.
  The inconsistent rollback behaviour related to co-located
  client requester and service provider was due to a header tag
  being absence from a response, causing the client to incorrectly
  identify a transaction integrity issue, and marked the
  transaction for rollback only.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Web Services-Atomic Transaction is      *
  *                      incorrectly rolledback at client        *
  *                      requester if a SOAP Fault is received   *
  *                      and the requester and provider reside   *
  *                      on the same JVM.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  By default, all SOAP Faults received by the Web Services-Atomic
  Transaction (WS-AT) handlers at the client requester are
  delegated up to the application code to decide whether to mark
  the transaction as rollback only, or to continue with normal
  processing flow.
  However, if the WS-AT handlers at the client requester detects
  that there is evidence that the transactional integrity of the
  WS-AT flow has been compromised, the WS-AT handler itself will
  mark the transaction for rollback only. The handlers test for
  transactional integrity by checking for the presence of various
  header tags in the SOAP response.
  The inconsistent rollback behaviour related to co-located
  client requester and service provider was due to a header tag
  being absence from a response, causing the client to
  incorrectly identify a transaction integrity issue, and
  marked the transaction for rollback only.
  

Problem conclusion

• Ensure the SOAP server handler correctly adds
  necessary imported header tag when Web Services requester and
  provider are located on the same jvm.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.8. and 8.5.5.2. Please refer to the Recommended
  Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM93219

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP