IZ27873: DATAFLOWENGINE THREAD MAY NOT RELEASE ALL RESOURCES WHEN FLOW IS REDEPLOYED

WebSphere Message Broker V6.1 - Fix Pack 6.1.0.7

APAR status

• Closed as program error.

Error description

• DataFlowEngine thread may not release all resources when flow is
  redeployed
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Message Broker V6.x.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Redeploying a flow which is currently   *
  *                      active (a hot deploy) may result in     *
  *                      the deployment hanging.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a flow is redeployed the Configuration Manager sends a
  message to the Broker's Admin Agent which in turn instructs
  the Execution Group to delete and then replace the affected
  nodes. If the flow is running when the redeployment occurs
  then its threads are stopped, their resources are released and
  the threads returned to a thread pool for re-use. The problem
  is that the first thread is not properly cleaned up and this
  can lead to a situation in which the deployment hangs waiting
  endlessly for that thread to release its resources.
  

Problem conclusion

• WebSphere Message Broker has been modified so that the problem
  no longer occurs.
  

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