]
Jesper Pedersen closed JBJCA-694.
---------------------------------
Resolution: Rejected
Use the forum discussions:
SonicMQ RA in JBoss7 showing lots of IJ000612 warnings (Destroying
connection that could not be successfully matched)
---------------------------------------------------------------------------------------------------------------------
Key: JBJCA-694
URL:
https://issues.jboss.org/browse/JBJCA-694
Project: IronJacamar
Issue Type: Bug
Affects Versions: 1.0.5.Final
Environment: Linux *2.6.32-71.29.1.el6.x86_64 #1 SMP x86_64 x86_64 x86_64
GNU/Linux
java version "1.6.0_27"
Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
JBoss 7.1.0.Alpha2 AS with current code from git
Reporter: Robert Stupp
Assignee: Jesper Pedersen
Basic integration of SonicMQ RA (version 8.5) works.
But when using JMeter with many parallel requests provoke a lot of these warnings:
{noformat}
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(a)5cf96bbc
pad=false overrideRmValue=false productName=java:/XAConnectionFactory
productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
{noformat}
With tracing enabled, JCA core connection manager tells this (before the message above):
{noformat}
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(a)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(a)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(a)5cf96bbc
pad=false overrideRmValue=false productName=java:/XAConnectionFactory
productVersion=java:/XAConnectionFactory jndiName=java:/XAConnectionFactory] txSync=null]
{noformat}
-----------------------------------------
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:
{noformat}
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(a)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(a)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(a)2429c748
pad=false overrideRmValue=false productName=SonicMQ productVersion=8.5.377
jndiName=java:/XAConnectionFactory] txSync=null]
... (17 more)
{noformat}
I am not sure whether this is caused by ironjacamar or JBoss7 code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: