Fixes are available
APAR status
Closed as program error.
Error description
In cases where a UTF8 BOM (Byte Order Mark) prefix is split across different TCP packets and DataPower is parsing the input as XML, DataPower will log a parsing error.
Local fix
If using a Microsoft TLS client, forcing TLS 1.2 can avoid this issue. This can be worked around on DataPower by changing your service configuration to non-xml input, and parsing the input into a buffer using Gatewayscript.
Problem summary
Affected is parsing of UTF8 BOM prefixed XML. In case XML message is split on several TCP packets, and first packet does not contain full UTF8 BOM, DataPower generates a parse error.
Problem conclusion
Fix is available in 7.5.0.16, 7.5.1.15, 7.5.2.15, 7.6.0.8 and 7.7.1.0 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Temporary fix
Comments
APAR Information
APAR number
IT21452
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-14
Closed date
2017-11-23
Last modified date
2018-06-21
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
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
R710 PSY
UP
R720 PSY
UP
R750 PSY
UP
R751 PSY
UP
R752 PSY
UP
R760 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.2"}]
Document Information
Modified date:
28 September 2021