IC88132: SOAPASYNCRESPONSE FAILS TO COPY WS-ADDRESSING TO LE

WebSphere Message Broker V8.0 - Fix Pack 8.0.0.2

APAR status

• Closed as program error.

Error description

• User has a SOAPAsyncResponse with validation enabled and
  'Place WS-Addressing Headers into LocalEnvironment' checked.
  An inbound response message causes a schema validation error.
  
  With Parse timing 'on demand' we propagate to the Out
  terminal. The LE includes the WS-Adrressing headers. The body
  parse fails, so we bounce back and propagate to the catch
  terminal with a RecoverableException. The LE still contains
  the WS-Addressing headers. But with Parse timing 'immediate'
  we propagate the Exception to the Failure terminal, this time
  the LE is missing.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker with SOAPAsyncResponse
  nodes.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM SUMMARY:
  If a user has a SOAPAsyncResponse node with validation enabled
  and 'Place WS-Addressing Headers into LocalEnvironment' checked,
  it is observed that the WS-Addressing headers are never placed
  inside the LocalEnvironment tree when a validation error happens
  and the parse timing is 'immediate'.
  

Problem conclusion

• WebSphere Message Broker has been modified to place the
  WS-Addressing headers to the LocalEnvironment tree
  irrespective of the parsing/validation outcome.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v8.0
  --------           --------------------
  Multiplatforms     8.0.0.2
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  WEB MESSAGE BRO

• Fixed component ID

  5724J0520

Applicable component levels

• R800 PSY

     UP