IT18930: IIB v10 ADMINISTRATION REQUESTS CAUSE MEMORY LEAK IN BIPBROKER PROCESS

APAR status

• Closed as program error.

Error description

• The bipbroker process maintains an in-memory cache of all of a
  brokers configuration data.  This cached data is used to provide
  information to the Integration API and REST APIs and as such
  provides the information displayed in the web user interface
  (WebUI) and Toolkit.
  
  The cache is built on start-up of the broker and is refreshed
  whenever any administration request is successfully completed
  that updates the brokers configuration.  If a brokers
  configuration contained any monitoring event definitions or had
  any WebUI users defined, then a memory leak would occur whenever
  the cache was refreshed.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10.0 with monitoring event
  definitions or web user interface (WebUI) users defined
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The bipbroker process maintains an in-memory cache of all of a
  brokers configuration data.  This cached data is used to provide
  information to the Integration API and REST APIs and as such
  provides the information displayed in the web user interface
  (WebUI) and Toolkit.
  
  The in-memory cache of an Integration Node (broker) is built on
  start-up and refreshed whenever any administration request that
  updates the configuration is successfully completed.  If a
  configuration contains any monitoring event definitions or has
  any web user interface (WebUI) users defined, then a memory leak
  will occur whenever the cache is refreshed.
  
  A large number of eye catchers appeared in the core dumps
  produced for the following objects, representing monitoring
  event and WebUI user definitions in the cache:
  ME17, ME23, DMEX, DMOB, ME21, ME20, ME26, ME25, ME24, ME32, DMWU
  
  High CPU in the bipbroker process was experienced when issuing
  the mqsiwebuseradmin commands to create or delete WebUI users,
  due to a full cache refresh taking place when making updates.
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The memory leak  in the configuration cache has been fixed and
  the scope of the cache refresh when a mqsiwebuseradmin command
  is issued has been reduced.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.8
  
  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 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

  5724J0540

Applicable component levels

• RA00 PSY

     UP