Hi,
Our basic integration of SonicMQ RA (version 8.5) works. The Resource Adapter containing the SonicMQ RA deploys without errors. Additionally we have a small "service", that adds the required JMS destinations to the JNDI environment (startup hook). Both the RA and the "service" use a module containing the required Sonic jar files.
Receiving JMS messages using a Message Driven Bean works fine. Sending JMS messages works as well as receiving JMS messages - either programmatically or via the SonicMQ JMS test tool. As long as no concurrent threads are running...
The JBoss7 version we are using is the latest code from GIT as of 2011/10/28. This version uses IronJacamar 1.0.5.Final. Older versions of AS7 did not work with RAs.
There are two situations where (nearly) the same WARN is logged.
1. Upon startup when the SonicMQ RA is used first. It prints one IJ000612 warning for each connection in the pool (-> pool min-size)
2. Occasionally when multiple threads are sending JMS messages concurrently, IJ000612 warnings are logged. It seems, that the http worker thread hangs when such a message is logged.
For situation #2 : using JMeter with many parallel requests a lot of these warnings are logged:
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0 lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90 xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@5cf96bbc pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
With tracing enabled, JCA core connection manager tells this (before the message above):
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) connectionClosed
called mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) unregisterConnection:
0 handles left
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10) delisting
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0
lastUse=1319815538458 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@5cf96bbc
pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory
jndiName=java:/XAConnectionFactory] txSync=null]
17:25:38,487 TRACE [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (http--0.0.0.0-8080-10)
isManagedConnectionFree=true mc=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612:
Destroying connection that could not be successfully matched:
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0
lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@5cf96bbc
pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory
jndiName=java:/XAConnectionFactory] txSync=null]
... (somthing else happens in other threads) ...
17:25:38,489 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-5) IJ000612:
Destroying connection that could not be successfully matched:
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7df5f91c[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@24f1c9c6 connection handles=0
lastUse=1319815538489 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@1fb5dddf[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@5cf96bbc
pad=false overrideRmValue=false productName=java:/XAConnectionFactory productVersion=java:/XAConnectionFactory
jndiName=java:/XAConnectionFactory] txSync=null]
For situation #1:
Related to the above (but slightly different messages (productName, productVersion):
The first request (after JBoss 7 startup) issues exactly as many of these warnings as the configured minimum pool size. For example: min-size=20 forces 20 of the following messages:
17:18:21,545 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612:
Destroying connection that could not be successfully matched:
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7d3e3b95[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@b9f370 connection handles=0
lastUse=1319815093744 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@301d3e6f[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@4fee0216
pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
17:18:21,547 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612:
Destroying connection that could not be successfully matched:
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@12cb1b59[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@547079b2 connection handles=0
lastUse=1319815093742 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@2445c06d[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@5f5c46b5
pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
17:18:21,550 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (http--0.0.0.0-8080-1) IJ000612:
Destroying connection that could not be successfully matched:
org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@232645fc[state=NORMAL managed
connection=com.sonicsw.sonicmq.j2ee.jmsra.impl.JMSSessionManagedConnection@25bcb56b connection handles=0
lastUse=1319815093740 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@6dbd726 pool internal
context=org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool@2fb8c90
xaResource=XAResourceWrapperImpl@82a9728[xaResource=com.sonicsw.sonicmq.j2ee.jmsra.impl.XAResourceWrapper@2429c748
pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377 jndiName=java:/XAConnectionFactory] txSync=null]
... (17 more)
I am not sure whether this is caused by ironjacamar or JBoss7 code.