IZ44920: SUBSCRIBE MEMORY LEAK WHEN STOPPING A JMS APP IN AN ABNORMAL WAY

WebSphere Message Broker V6.1 - Fix Pack 6.1.0.7

APAR status

• Closed as program error.

Error description

• The customer is issuing a kill -9 through a script on their
  subscribing JMS application causing their memory usage to grow.
  Killing the subscribing application rather than closing the
  subscription seems to be the cause for the memory growth.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Message Broker and    *
  *                 Publish and Subscribe.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The default execution group increases   *
  *                      in memory until it abends.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Subscriptions created by an MQ JMS application
  create a number of durable subscriptions. If the
  application is shutdown using a kill -9, then
  MQ JMS will send a message to the broker when the
  application terminates abnormally which causes
  a memory leak on the default execution group.
  

Problem conclusion

• MQ JMS sent a defered put mesage to the default
  execution group if an application ends abnormally and
  this caused a memory leak.
  The Message Broker code was modified to fix this memory
  leak.
  

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

  WMB SOL SPARC

• Fixed component ID

  5724J0502

Applicable component levels

• R100 PSY

     UP