Troubleshooting
Problem
You access WebSphere MQ V6.0 queues using JMS from a Java™ application which sits in EJB beans in WebSphere Application Server. The application has been running for a number of years with no errors, in WebSphere Application Server V5. You are now trying to run exactly the same Java application on WebSphere Application Server V6. The bean creates a connection to a queue. It then creates a session on this connection, using: queueSession = queueConnection.createQueueSession(transactional,Session.AUTO_ACKNOWLEDGE); It then creates a sender, and places a message on the queue. When access is completed, the session is closed, but the connection is left open for re-use. This is done for performance reasons.The application which is deployed on WebSphere Application Server V6 fails at the point when it tries to re-use a connection on the queue. The createQueueSession method fails, creating an associated ffdc log. The relevant section of the failing method stack from the ffdc log shows: javax.jms.IllegalStateException com.ibm.ejs.jms.JMSQueueConectionHandle.createQueueSession 159Exception = javax.jms.IllegalStateExceptionSource = com.ibm.ejs.jms.JMSQueueConnectionHandle.createQueueSessionprobeid = 159 Stack Dump = javax.jms.IllegalStateException: Connection closed at com.ibm.ejs.jms.JMSConnectionHandle.checkOpen(JMSConnectionHandle.java:671) at com.ibm.ejs.jms.JMSQueueConnectionHandle.createQueueSession( JMSQueueConnectionHandle.java:172) at com.littlewoods.enterprise.framework.services.AsyncPutterBean.getSession (Unknown Source) at com.littlewoods.enterprise.framework.services.AsyncPutterBean.GenericPut (Unknown Source)
To view more of this document
Was this topic helpful?
Document Information
More support for:
WebSphere MQ
Software version:
6.0
Operating system(s):
AIX, HP-UX, Linux, Solaris
Document number:
350335
Modified date:
03 March 2025
UID
swg21267957