Cached-connection-manager DEBUG connection closure could be too eager with enlistment-trace==false -------------------------------------------------------------------------------------------------- Key: WFLY-10414 URL: https://issues.jboss.org/browse/WFLY-10414 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 13.0.0.Beta1, 12.0.0.Final Reporter: Stefano Maestri Assignee: Stefano Maestri Labels: gss There is some corner cases in which IJ isn't able to avoid IJ000100 (closing connection for you) on connection already marked as invalid and firing IJ000100 closing it, even if the connection would be closed as invalid immediately after. It doesn't create problems to the connection pool, but the redundant WARN isn't useful and could be read as connection leak. It happens only with enlistment-trace=false (which is default since 7.2) set for the involved datasource