Fixes are available
APAR status
Closed as program error.
Error description
Certain Unicode characters can cause issues when parsing a message into a ServiceMessageObject. While the flow can continue to work in this circumstances, if mediation trace is enabled then a Runtime Exception will be thrown that stops the flow.
Local fix
n/a
Problem summary
**************************************************************** USERS AFFECTED: Users of WebSphere Enterprise Service Bus and Business Process Manager v7.5 or v8 who use Unicode characters in messages. **************************************************************** PROBLEM SUMMARY: When using messages that contain Unicode characters that are invalid in XML, such as 0x1d, with mediation tracing enabled then the flow would be stopped by an exception if a Service Invoke primitive is used in the flow.
Problem conclusion
The Service Invoke primitive has been changed so the tracing code does not disrupt the flow. This code fix was targeted to be included in the following fix packs: 7.5.1 Fix Pack 2 (v7.5.1.2) 8.0.1 Fix Pack 3 (BPM v8.0.1.3)
Temporary fix
Comments
APAR Information
APAR number
IC97572
Reported component name
WEB ESB FOR WIN
Reported component ID
5724I8200
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-11
Closed date
2013-12-18
Last modified date
2013-12-18
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 ESB FOR WIN
Fixed component ID
5724I8200
Applicable component levels
R751 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"751","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 March 2023