Fixes are available
APAR status
Closed as program error.
Error description
If a WebSphere Enterprise Service Bus or WebSphere Process Server v6.2 or V7 flow contains a mediation module with one or more subflow mediation primitives with multiple paths through the flow to reach that primitive this will involve a large memory usage and may result in an OutofMemoryError exception.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Enterprise Service Bus * * or WebSphere Process Server v6.2 or v7 who * * use a mediation module with subflow * * mediation primitives that can be invoked * * by multiple paths in the flow and who are * * seeing OutOfMemoryError exceptions. * **************************************************************** * PROBLEM DESCRIPTION: When a mediation module contains a * * subflow that can be invoked through * * multiple paths this can result in * * excessive memory usage as a copy of * * the subflow is loaded into memory for * * each possible branch of the flow that * * can invoke it. This can result in an * * OutOfMemoryError exception being seen. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a WebSphere Enterprise Server Bus or WebSphere Process Server flow contains a mediation module with a subflow mediation primitive where there are multiple paths through the flow to reach that primitive then on first invocation of the mediation flow, a copy of the subflow is loaded in to memory for each path. This results in excessive memory usage. This may result in an OutOfMemoryError Exception depending on the number of subflow mediation primitives, by the complexity of those subflows, and by having multiple concurrent requests. A heap dump will show large numbers of RequestFlowModel objects.
Problem conclusion
The code was modified such that each subflow is only loaded into memory once. There are no known side effects associated with this fix. There is no known alternative workaround should you encounter this problem. This code fix was targeted to be included in the following fix packs: 6.2.0 Fix Pack 3 (v6.2.0.3) 7.0.0 Fix Pack 2 (v7.0.0.2)
Temporary fix
Comments
APAR Information
APAR number
IC66490
Reported component name
WEB ESB FOR WIN
Reported component ID
5724I8200
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-19
Closed date
2010-03-02
Last modified date
2010-04-22
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
R100 PSN
UP
R200 PSN
UP
R300 PSN
UP
R612 PSN
UP
R620 PSY
UP
R700 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":"6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 March 2023