TJ Cowhey created JBJCA-1390: -------------------------------- Summary: BlockingFailureCount not tracking IJ000655 errors Key: JBJCA-1390 URL: https://issues.jboss.org/browse/JBJCA-1390 Project: IronJacamar Issue Type: Bug Environment: JBoss Enterprise Application Platform 7 Reporter: TJ Cowhey The Byteman rule below [1] (and a test-connection from the web console for the ExampleDS) verifies the finding that org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool is the default pool now. As of the latest released code base (EAP 7.2 CP1), the timeout counter increment performed in the array list version of the pool [2] is omitted from the linked dequeue based version [3]. This looks like a bug. This results in BlockingFailureCount not tracking IJ000655 errors. [1] Byteman rule showing which managed connection pool implementations are created RULE org.jboss.jca.core.connectionmanager.pool.mcp.ManagedConnectionPool INTERFACE org.jboss.jca.core.connectionmanager.pool.mcp.ManagedConnectionPool METHOD <init> AT EXIT IF true DO traceStack("[BMAN] "); ENDRULE [2] https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.15.Final/... [3] https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.4.15.Final/... -- This message was sent by Atlassian Jira (v7.12.1#712002)