Fixes are available
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 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
APAR status
Closed as program error.
Error description
A JAX-WS or SAAJ web service can return a SOAP 1.2 Fault to the client, such as the following: <soap:Fault> <soap:Code> <soap:Value>soap:Receiver</soap:Value> <soap:Subcode> <soap:Value>q0:Error</soap:Value> </soap:Subcode> </soap:Code> <soap:Reason> <soap:Text xml:lang="en">Example reason<soap:Text> </soap:Reason> <soap:Node>This is a node</soap:Node> <soap:Role>This is a role</soap:Role> </soap:Fault> Application developers can set values for these child elements by using the javax.xml.soap.SOAPFault API described at http://www.j2ee.me/javaee/5/docs/api/javax/xml/soap/SOAPFault.ht ml. The JAX-WS runtime does not honor the user-specified values for Node and Role elements. The SOAP Fault is serialized properly; however, when the client intercepts the javax.xml.soap.SOAPFault and gets the Role and Node, the values are incorrect. In other words, these methods: SOAPFault.getFaultRole() SOAPFault.getFaultNode() would not return the values that the user had originally specified.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of JAX-WS and SAAJ web services in * * IBM WebSphere Application Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: A SOAP 1.2 Fault might contain * * incorrect values for Role and Node * * child elements. * **************************************************************** * RECOMMENDATION: Install a fixpack that contains this APAR. * **************************************************************** A JAX-WS or SAAJ web service can throw a javax.xml.soap.SOAPFaultException that is created with a user-created javax.xml.soap.SOAPFault. The web service application developer can specify that this SOAPFault is in accordance with the SOAP 1.2 specification, using the javax.xml.soap.MessageFactory.newInstance(String protocol) method. This results in a SOAP 1.2 Fault being sent back to the client. In addition to the mandatory Code and Reason child elements, a SOAP 1.2 Fault can have child elements Role and Node, which are optional. For example: <soap:Fault> <soap:Code> <soap:Value>soap:Receiver</soap:Value> <soap:Subcode> <soap:Value>q0:Error</soap:Value> </soap:Subcode> </soap:Code> <soap:Reason> <soap:Text xml:lang="en">Example reason<soap:Text> </soap:Reason> <soap:Node>This is a node</soap:Node> <soap:Role>This is a role</soap:Role> </soap:Fault> Application developers can set values for these child elements by using the javax.xml.soap.SOAPFault API described at http://www.j2ee.me/javaee/5/docs/api/javax/xml/soap/SOAPFault.ht ml. The JAX-WS runtime does not honor the user-specified values for Node and Role elements. The SOAP Fault is serialized properly; however, when the client intercepts the javax.xml.soap.SOAPFault and gets the Role and Node, the values are incorrect. In other words, these methods: SOAPFault.getFaultRole() SOAPFault.getFaultNode() would not return the values that the user had originally specified.
Problem conclusion
The JAX-WS runtime was fixed to honor the user-defined values for Role and Node child elements. APAR PK98611 fixes this same problem for the V6.1 WebSphere Application Server Feature Pack for Web Services. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. 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
PK98813
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-16
Closed date
2009-11-05
Last modified date
2009-11-05
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021