[ https://issues.jboss.org/browse/JBJCA-1344?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on JBJCA-1344: --------------------------------------- [~simkam] Yes, the analysis is correct, that concurrent behavior is causing the 1 destroyed statistics. What I need to check with you and [~maeste] is: is this behavior unexpected? Synchronizing both threads would just result in loss of performance and defeat the purpose of the entire synchronization algorithm in the MCP, so I see that as a no no. The other possibility for fixing the statistics is just not adding to the destroyed statistics count when the connection is destroyed in the given scenario. But is the statistics supposed to hide that info, given that the statistics will show that there was an extra connection created (at https://github.com/ironjacamar/ironjacamar/blob/1.4/core/src/main/java/or... and at https://github.com/ironjacamar/ironjacamar/blob/1.4/core/src/main/java/or...). I'm afraid that omitting the destroyed connection from the statistics will just leave it inconsistent. And, if to make it consistent will also mean not incrementing the created connection statistics, it will still be inconsistent with the fact that there was an actual connection created. -- This message was sent by Atlassian JIRA (v7.2.3#72005)