Fixes are available
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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
The Web Service Interoperability Basic Profile 2.0 Specification (WS-I BP 2.0) has the following requirement: Rule R1019: A receiver must ignore the encoding pseudo-attribute of the envelope's XML declaration. Here is an example message with conflicting character set encoding values. Note the that the charset value on the CONTENT-TYPE is "UTF-16" and the ?xml encoding is "UTF-8": HTTP/1.1 CONTENT-TYPE: text/xml;charset="UTF-16" .. <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:tem="http://tempuri.org/"> ... </soap:Envelope> Here is the invalid response received from the JAX-WS Web service: Response HTTP/1.1 500 Error CONTENT-TYPE: text/xml; charset=UTF-16 ... <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault xmlns:axis2ns2="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>axis2ns2:Client</faultcode> <faultstring>Character Set Encoding from transport information [UTF-8] does not match with character set encoding in the received SOAP message [UTF-16]</faultstring> <detail/> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 * * administrators of JAX-WS Web services * **************************************************************** * PROBLEM DESCRIPTION: The JAX-WS Web service should * * tolerate an inbound message that has * * mixed character encodings. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this APAR * **************************************************************** The Web Service Interoperability Basic Profile 2.0 Specification (WS-I BP 2.0) has the following requirement: Rule R1019: A receiver must ignore the encoding pseudo-attribute of the envelope's XML declaration. Here is an example message with conflicting character set encoding values. Note the that the charset value on the CONTENT-TYPE is "UTF-16" and the ?xml encoding is "UTF-8": HTTP/1.1 CONTENT-TYPE: text/xml;charset="UTF-16" .. <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:tem="http://tempuri.org/"> ... </soap:Envelope> Here is the invalid response received from the JAX-WS Web service: Response HTTP/1.1 500 Error CONTENT-TYPE: text/xml; charset=UTF-16 ... <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault xmlns:axis2ns2="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>axis2ns2:Client</faultcode> <faultstring>Character Set Encoding from transport information [UTF-8] does not match with character set encoding in the received SOAP message [UTF-16]</faultstring> <detail/> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>
Problem conclusion
The JAX-WS runtime is changed to remove the invalid checking. The Web service will successfully process the inbound message that contains mixed character encodings. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM21946
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
2010-09-04
Closed date
2010-09-10
Last modified date
2010-09-10
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