Some more details because I also upgraded to the latest WMQ resource adapter without success.
I tested against
- JBoss EAP 6.2.0 Release
- Websphere MQ Resource Adapter 18.104.22.168 and 22.214.171.124
It is relatively easy to reproduce this behavior with a trivial MDB and minimal configuration changes against the delivered configuration file. This makes me nervous since the JBoss 6.2.0 EAP Release Notes state:
WebSphere MQ Certification
Integration with WebSphere MQ via the WebSphere MQ resource adapter has been tested and certified.
Against which WMQ version was the certification done?
Behavior can be reproduced with the following steps:
(1) Deploy wmq.jmsra.rar
(2) Setup MDB section in standalone-full.xml to use wmq.jmsra.rar as resource adapter
(3) Setup resource adapter section in standalone-full.xml with an admin-object for an MDB
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/queue/CEIMOCKRequestQueue" pool-name="CEIMOCKRequestQueuePool">
(4) Deploy a simple application with an MDB referencing the admin-object above
(5) Start JBoss against the edited standalone-full.xml and wait about two minutes for the first exception to appear.
Any help/hint is greatly appreciated.
Not sure if you got passed this issue already, but we ran into 2 seperate issues with regards to the interaction of the JBoss JCA and the periodic recovery fix that first showed up in the 6.1.1 release.
The first issue was the exception you have above, which was fixed in the 126.96.36.199 version of the Websphere resource adapter. This left us with just a warning in the logs after that which was fixed by a subsequent patched Resource Adapter provided by IBM.