APAR status
Closed as fixed if next.
Error description
In IBM Integration Bus v10, a message set was only loaded into memory when it was first referenced by a message flow. This means the memory and CPU cost for loading a message set is only incurred if and when the message set is actually used at runtime. In IBM App Connect Enterprise v11 and v12, all .dictionary files deployed to an integration server are loaded into memory during start up regardless of whether they are actually used in a message flow. This means that the large CPU and memory cost of loading a dictionary is incurred for every dictionary during every start up and deploy. This change in behaviour can lead to excessive CPU and memory usage especially when large numbers of message sets are deployed in static libraries but then not used at runtime.
Local fix
N/A
Problem summary
**************************************************************** USERS AFFECTED: All users of MRM message sets in IBM App Connect Enterprise v11 and v12 Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: In IBM Integration Bus v10, a message set was only loaded into memory when it was first referenced by a message flow. This means the memory and CPU cost for loading a message set is only incurred if and when the message set is actually used at runtime. In IBM App Connect Enterprise v11 and v12, all .dictionary files deployed to an integration server are loaded into memory during start up regardless of whether they are actually used in a message flow. This means that the large CPU and memory cost of loading a dictionary is incurred for every dictionary during every start up and deploy. This change in behaviour can lead to excessive CPU and memory usage especially when large numbers of message sets are deployed in static libraries but then not used at runtime.
Problem conclusion
IBM App Connect Enterprise 11.0.0.14 and 12.0.2.0 introduces a new configuration option in the MRM resource manager section of the server.conf.yaml file. This new resource manager exposes an option "messageSetLoadStrategy" which can either take the value of "onServerStart" (the default) or "onFirstMessage" with the following meanings: * "onServerStart" - All MRM message sets are loaded immediately when the integration server is started or a new message set is deployed. * "onFirstMessage" - An MRM message set is only loaded when it is first used during message processing. Affected users should set this new property to "onFirstMessage" to defer the CPU and memory overhead to message flow runtime rather than startup/deploy. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.0.0.14 v12.0 12.0.2.0 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
IBM App Connect Enterprise 11.0.0.14 and 12.0.2.0 introduces a new configuration option in the MRM resource manager section of the server.conf.yaml file. This new resource manager exposes an option "messageSetLoadStrategy" which can either take the value of "onServerStart" (the default) or "onFirstMessage" with the following meanings: * "onServerStart" - All MRM message sets are loaded immediately when the integration server is started or a new message set is deployed. * "onFirstMessage" - An MRM message set is only loaded when it is first used during message processing. Affected users should set this new property to "onFirstMessage" to defer the CPU and memory overhead to message flow runtime rather than startup/deploy. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.0.0.14 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 ---------------------------------------------------------------
APAR Information
APAR number
IT38398
Reported component name
APP CONNECT ENT
Reported component ID
5724J0550
Reported release
B00
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-09-16
Closed date
2022-02-04
Last modified date
2022-03-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]
Document Information
Modified date:
11 March 2022