PH62686: WS-AT FAILS WHEN DOWNSTREAM RUNTIME IS NON-LIBERTY

APAR status

• Closed as program error.

Error description

• WS-AT fails when downstream runtime is a non-Liberty system.
  
  The transaction in the Liberty Application Server times out.
  
  The Liberty Application Server generates a SOAPFault with
  faultstring "txID is NULL" in response to an inbound WS-AT
  RegisterOperation.  For example:
  
  <soap:Envelope
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
      <Action
  xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-o
  pen.org/ws-tx/wscoor/2006/06/RegistrationPortType/RegisterOperat
  ion/Fault/WSATException</Action>
      <MessageID
  xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:4321ABCD-1
  A11-22B2-C1CC-D2222DD222DD</MessageID>
      <To
  xmlns="http://www.w3.org/2005/08/addressing">http://www.w3.org/2
  005/08/addressing/anonymous</To>
      <RelatesTo
  xmlns="http://www.w3.org/2005/08/addressing">uuid:1234ABCD-1234-
  4321-A123-11AA11111111</RelatesTo>
    </soap:Header>
    <soap:Body>
      <soap:Fault>
        <faultcode>soap:Server</faultcode>
        <faultstring>txID is NULL</faultstring>
      </soap:Fault>
    </soap:Body>
  </soap:Envelope>
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Liberty Application Server users  *
  *                  of the WS-AT Feature                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Transaction propagation via WS-AT to    *
  *                      a SOAP Web Service hosted on a          *
  *                      non-Liberty platform results in a       *
  *                      transaction timeout.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The fix for
  https://github.com/OpenLiberty/open-liberty/issues/27552
  omitted the GlobalID reference parameter from the
  RegistrationService's EPR that it sends in the WS-AT
  CoordinationContext to the downstream server.
  This caused a regression in the registration process used by
  WS-AT when the downstream WS-AT platform is non-Liberty,
  causing Liberty to fail the requested registration with a
  SOAPFault containing the faultstring "txID is NULL" and
  resulting in the transaction timing out.
  

Problem conclusion

• https://github.com/OpenLiberty/open-liberty/issues/29127
  contains the fix for this APAR, adding the GlobalID reference
  parameter back into the Registration Service's EPR.
  
  The fix for this APAR is targeted for inclusion in fix pack
  24.0.0.9. 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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels