IC90273: USING LOG ACTION ON NON UTF-8 ENCODED CONTEXT IN ORDER TO LOG INTERNALLY MAY CAUSE AN UNEXPECTED RESTART
Fixes are available
Fix packs for DataPower Low Latency Appliance version 5.0
Fix packs for DataPower B2B appliances version 5.0
Fix packs for DataPower Integration appliances version 5.0
Fix packs for DataPower XML Accelerator appliances version 5.0
Fix packs for DataPower XML Security Gateway appliances version 5.0
Fix packs for DataPower Service Gateway appliances version 5.0
Fix packs for DataPower Service Gateway XG45 Virtual Edition version 5.0
Fix packs for DataPower Integration Appliance XI52 Virtual Edition version 5.0
Closed as program error.
An unexpected restart may occur when using a Log action on Non-UTF-8 encoded context data.
Only log UTF-8 encoded contexts to the DataPower internal log. Or log non-UTF-8 data to a remote target.
Affected is the use of Log Action without Destination set (to DataPower internal log) for a Non-Binary context. DataPower tries to send a context to the Log in the encoding specified for that context, although DataPower's internal log requires UTF-8 encoded data. This may result in "interesting looking" or truncated log entries, or even in restart of the appliance.
Now a Non-Binary context is sent to the DataPower internal log as UTF-8 encoded, regardless of the encoding specified for that context. Fix is available in 126.96.36.199, 188.8.131.52 and 184.108.40.206. For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
More support for:
WebSphere DataPower Integration Appliance XI52
Software version: 5.0.0
Reference #: IC90273
Modified date: 15 May 2013