APAR status
Closed as program error.
Error description
In rare occurrences, a message flow using an XSL Transform node configured to use the TLOG to POSLOG XSLT stylesheets shipped with the IBM Integration Bus Retail Pack can take a relatively long time to process certain messages, while using a large amount of heap to complete the transaction. Normally, processing successfully finishes eventually and no disruption is caused to the concurrent processing of other messages. However, the problem can indirectly trigger a Java OutOfMemoryError if several problematic messages are being processed at the same time.
Local fix
The problem can sometimes be mitigated by increasing the Java heap size available to IBM Integration Bus, or setting the "Stylesheet cacheevel" on the XSL Transformation node to 0. However, this may reduce performance and may not be effective in all situations.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus using XSL Transformation nodes with sufficiently complex stylesheets. Platforms affected: AIX, Linux on Power platform, Linux on x86 platform, Linux on x86-64 platform, Linux on zSeries platform, Windows on x86 platform, Windows on x86-64 platform **************************************************************** PROBLEM DESCRIPTION: In rare occurrences, a message flow using an XSL Transform node configured to use the TLOG to POSLOG XSLT stylesheets shipped with the IBM Integration Bus Retail Pack can take a relatively long time to process certain messages, while using a large amount of heap to complete the transaction. Normally, processing successfully finishes eventually and no disruption is caused to the concurrent processing of other messages. However, the problem can indirectly trigger a Java OutOfMemoryError if several problematic messages are being processed at the same time.
Problem conclusion
The product has been updated with a new level of the Java Runtime Environment that includes an XSLT processor capable of transforming messages with stylesheets that are known to have been problematic using the default XSLT transformation engine. It is now possible to switch to the transformation engine that ships with the JRE and correctly process previously affected XML messages correctly. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 9.0.0.6 v10.0 10.0.0.4 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT12814
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-16
Closed date
2016-03-07
Last modified date
2016-03-07
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
INTEGRATION BUS
Fixed component ID
5724J0530
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020