Garbage collection alone cannot release all WebSphere MQ resources in a timely manner, especially if an application creates many short lived JMS objects at the session level or lower. It is therefore important for an application to call the appropriate close() method to close a Connection, Session, MessageConsumer, or MessageProducer object when it is no longer required.
If an application using WebSphere MQ JMS finishes without calling Connection.close(), some JVMs appear to hang. If this problems occurs, you can end the JVM by entering Ctrl-C. To avoid the problem in the future, consider modifying the application to include a call to Connection.close().
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzaw1377 |