IJ000612: Destroying connection that could not be successfully matched

[ramiseesniblic]

I am using JBoss EAP 6 with a connection to Websphere MQ V8 (using JMS).

I am getting the following WARN message and I cannot figure out what could be causing it.

2015-06-19 14:13:31,808 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (Local_Worker-6) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@7b53f70a[state=NORMAL managed connection=com.ibm.mq.connector.outbound.ManagedConnectionImpl@457ff0c7 connection handles=0 lastUse=1434719611784 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@5f1fe575 pool internal context=SemaphoreArrayListManagedConnectionPool@9db6459[pool=WSMQJms] xaResource=XAResourceWrapperImpl@5298bc76[xaResource=com.ibm.mq.connector.xa.XARWrapper@c7d60a5 pad=false overrideRmValue=null productName=WebSphere MQ productVersion=1.5.2.1 09/08/17 08:25:15 jndiName=java:jboss/WSMQJms] txSync=null]

Can anyone help?

[ramiseesniblic]

Can anyone suggest any reasons / fixes for this?

[abhijithumbe]

When the ping invocation in isValidConnection() -- org/jboss/jca/adapters/jdbc/extensions/mysql/MySQLValidConnectionChecker.java fails, it returns an SQLException the message Destroying connection that could not be successfully matched is logged.

It is good to use validate-on-match rather than background-validation to reduce the risk at application code encountering a connection failure (validate-on-match will be enforced on each connection request whereas background-validation runs only periodically). The use of background validation is recommended only in cases where a very high frequency of connection requests occurs (in which case validation might be costly) but background validation has a higher risk that the application code may be given an invalid connection (since no check is done at the time of the request).

[ramiseesniblic]

Hello. Thank you for your reply.

I think that this message is not being caused by a SQLException as the warning is from the Websphere MQ connection pool. (Which is a resource adapter).  Is there any way that I can configure connection validation in the "connection-definition" section of my resource adapter? 

[ramiseesniblic]

Does anyone else have an in-site into this warning?

[ramiseesniblic]

Ok.  Found the issue.  It was when I was opening and then immediately closing the connection the WSMQ without sending any data.  For some unknown reason, this was causing the warning to appear.