Fixes are available
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
The Webservice response message may contain the following Fault... <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soape nv:Body> <soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/"><faul tcode>axis2ns1:MustUnderstand</faultcode><faultstring>Must Understand check failed for header soapenv :{http://schemas.xmlsoap.org/ws/2004/10/wscoor}CoordinationConte xt</faultstring><detail></detail></soapenv:Fault></soapenv:Body> </soapenv:Envelope> Another symptom that is possible is WTRN0006W messages which indicate that a transaction has timed out after a message is processed by a Service Integration Bus Resource Adapter Message Driven Bean.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * SIB-WS and SCA applications bound to the * * Service Integration Bus * **************************************************************** * PROBLEM DESCRIPTION: JAX-RPC request fails with * * SOAPFault with faultcode * * MustUnderstand * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PM90220 removed function that prevented the transaction context associated with the thread when the SIB Resource Adapter dispatches an inbound message from being propagated via WS-AT on JAX-RPC requests. As a result, transaction propagation may occur in instances where it previously did not resulting in unintended propagation of the transaction context. This may cause the JAX-RPC request to fail generating a SOAPFault containing the following faultstring: <faultstring>MustUnderstand check failed for header soapenv :{http://schemas.xmlsoap.org/ws/2004/10/wscoor}CoordinationConte xt</faultstring><detail></detail></soapenv:Fault></soapenv:Body> </soapenv:Envelope>
Problem conclusion
The transaction context associated with the thread when the SIB Resource Adapter dispatches an inbound message will not be propagated via WS-AT on JAX-RPC Web Service requests unless the transaction was imported from the inbound message. This reverts the change of behavior introduced by APAR PM90220 for transactions of this type. A JVM System Property has been provided to allow such transactions to be propagated via WS-AT as per the function delivered in APAR PM90220. To enable that behavior, set the JVM System Property com.ibm.ws.Transaction.wsat.allowSIBRAPropagation to a value of true. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.31, 8.0.0.9 and 8.5.5.3. 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 number
PI11879
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-17
Closed date
2014-03-03
Last modified date
2014-08-06
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022