Fixes are available
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
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
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.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
JMS message body is using the wrong character set, even though it has received the data correctly. Special characters are not correctly encoded. The 'String' object which contains the correct message contents is converted to a byte array by calling 'String.getBytes()', which uses the "default charset" of the Java VM, presumably ISO8859-1 in this case. Unfortunately special characters seem to get converted to a one byte representation during consumption of the message by listener port Which ultimately leads to an exception in the JAX-WS web service: org.apache.axis2.jaxws.ExceptionFactory logRootCause Root Cause:javax. xml.stream.XMLStreamException: An invalid XML character (Unicode: 0xffffffff) was found in the element content of the document.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * SOAP over JMS web services. * **************************************************************** * PROBLEM DESCRIPTION: JMS message body using the wrong * * character set, even though it has * * received the data correctly. Special * * characters are not correctly encoded. * **************************************************************** * RECOMMENDATION: * **************************************************************** During JMS message processing, the incoming message is converted to a byte array by calling 'String.getBytes()', which may transform the original characters in it incorrectly.
Problem conclusion
A new property com.ibm.ws.websvcs.transport.jms.ContentType is added to allow a user to customize the message encoding other than the JVM default value. The value of the property must be set as a standard charset name, such as UTF-8. The default value of this property is null. The following Knowledge Center topic describes how to set a JVM property: http://www- 01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphe re.base.doc/ae/xrun_jvm.html?cp=SSEQTP_8.5.5%2F1-17-5- 387&lang=en The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.12 and 8.5.5.8. 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
PI45126
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-07-17
Closed date
2015-09-23
Last modified date
2015-09-23
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022