IBM WebSphere DataPower SOA Appliance MQ Manager Object's connections are not closed as expected. - United States  TECHNOTE (FAQ)

QUESTION
 IBM WebSphere DataPower SOA appliance MQ Manager Object's connections are not closed as expected. This can happen when the mq-qm object uses the default value which is an empty string. 

CAUSE
DataPower MQ manager object's idle connection is not closed when using default cache timeout.

ANSWER
Change the cache timeout on the IBM WebSphere DataPower MQ manager (mq-qm) object. You can start using a value of 60 seconds as the suggestion. The best practice is to use a value which should be less than the KeepAlive Timeout of the MQ Queue Manager (qmgr).
What may be the cause of unclosed MQ object connections on DataPower? How can I resolve open MQ object connections that did not close out on DataPower?
Change the cache timeout on the IBM WebSphere DataPower MQ manager (mq-qm) object. You can start using a value of 60 seconds as the suggestion. The best practice is to use a value which should be less than the KeepAlive Timeout of the MQ Queue Manager (qmgr).