Inaccurate IJ000100 leak warnings in certain cases when using Cached Connection Manager debug in JBoss EAP 7.1
Issue
- The database has been shutdown and connection validation fails while getting a connection
- Cached connection manager debug has been enabled to check for leaks
-
The connection is reported as having been leaked though it was never returned to the component requesting it
... IJ000100: Closing a connection for you. Please close them yourself: org.jboss.jca.adapters.jdbc.jdk8.WrappedConnectionJDK8@55f66f3c: java.lang.Throwable: STACKTRACE at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.registerConnection(CachedConnectionManagerImpl.java:308) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:819) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138) at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64) at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ...
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 7.1
- IronJacamar (JCA) 1.4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.