When running the test-connection-in-pool() operation on the IBM WMQ RA connection pool the following warning gets logged in the server log

WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default-threads - 1) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@6fa3e73f[state=NORMAL managed connection=com.ibm.mq.jakarta.connector.outbound.ManagedQueueConnectionImpl@fccaa18 connection handles=0 lastReturned=1742978827865 lastValidated=1742978827865 lastCheckedOut=1742978827865 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@4c791637 mcp=SemaphoreConcurrentLinkedDequeManagedConnectionPool@9b2b189[pool=wmqQCF] xaResource=XAResourceWrapperImpl@55a47f07[xaResource=com.ibm.mq.jakarta.connector.xa.XARWrapper@35522461 pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p935-001-240405 su=_o1_M5vNNEe6mUKqTP0CEtw pn=com.ibm.mq.jakarta.connector/src/com.ibm.mq.jakarta.connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/wmq/MQCF] txSync=null]

The JBoss EAP standalone-full.xml config file is attached to the JIRA. The configuration appears to be working since I can deploy a MDB and consume and send messages to a queue in WMQ broker. IBM WMQ broker version is

bash-5.1$ dspmqver
Name: IBM MQ
Version: 9.4.2.0
Level: p942-L250214
BuildType: IKAP - (Production)
Platform: IBM MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 6.13.8-200.fc41.x86_64
O/S Details: Red Hat Enterprise Linux 9.5 (Plow)
InstName: Installation1
InstDesc: IBM MQ V9.4.2.0 (Unzipped)
Primary: N/A
InstPath: /opt/mqm
DataPath: /mnt/mqm/data
MaxCmdLevel: 942
LicenseType: Developer
ReleaseType: Continuous Delivery (CD)