Hi,
I have an app running on websphere 61 server and using jboss jbm as messaging provider. the app has been running file except yesterday an exception as below was thrown:
00022e1c MCWrapper E J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection com.ibm.ejs.jms.JMSManagedQueueConnection@75e875e8
managed connection factory = com.ibm.ejs.jms.GenericJMSManagedQueueConnectionFactory@239e239e
physical connection = JBossConnection->ConnectionDelegate[24117616, ID=f5ok2-4yp324jg-1-nw2ns0ig-9xv9s5-x5r3h3h4, SID=0]
credential = javax.resource.spi.security.PasswordCredential@3e0fddd0
open connection handles = [] from resource jms/XAConnectionFactory. Caught exception: javax.resource.spi.ResourceAdapterInternalException: Failed to stop connection on cleanup
at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException(JMSCMUtils.java:176)
at com.ibm.ejs.jms.JMSManagedConnection.cleanup(JMSManagedConnection.java:981)
at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1467)
at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:492)
at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1783)
at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:2301)
at com.ibm.ejs.j2c.ConnectionEventListener.connectionClosed(ConnectionEventListener.java:326)
at com.ibm.ejs.jms.JMSManagedConnection.handleClosed(JMSManagedConnection.java:1637)
at com.ibm.ejs.jms.JMSConnectionHandle.close(JMSConnectionHandle.java:564)
at org.springframework.jms.support.JmsUtils.closeConnection(JmsUtils.java:57)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:439)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:477)
at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:543)
at org.springframework.jms.core.JmsTemplate.convertAndSend(JmsTemplate.java:534)
at com.valueoptions.fileconnect.jms.FileConnectSender.sendFile(FileConnectSender.java:57)
at com.valueoptions.fileconnect.handler.JmsSenderFileHandler.handle(JmsSenderFileHandler.java:14)
This exception immediately followed an DB transaction rollback so I think maybe the DB transaction rollback triggered such an exception. And finally message listeners are stopped on that server.
Please help!