[embjopr-issues] [JBoss JIRA] Created: (EMBJOPR-93) AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed

AS5 plugin: The value of "Connections In Use Count" that gets displayed in the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-93 URL: https://jira.jboss.org/jira/browse/EMBJOPR-93 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss Branch_5_x r85739, embjopr r209 Reporter: Farah Juma Fix For: 1.2 Steps to reproduce: Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. Request multiple connections from the connection pool. Then, close a few of these connections. Perform the "List Formatted Sub Pool Statistics" operation for this datasource. The value of "Connections In Use Count" in the result of the operation is not updated to reflect the closed connections. For example, when min-pool-size=5, max-pool-size=20, and there are 10 connections in use, the following is the result of the "List Formatted Sub Pool Statistics" operation after closing 2 connections: Sub Pool Statistics: Sub Pool Count: 1 ------------------------------------------------------ Track By Transaction: true Available Connections Count: 12 Max Connections In Use Count:10 Connections Destroyed Count:0 **Connections In Use Count:10** Total Block Time:0 Average Block Time For Sub Pool:0 Maximum Wait Time For Sub Pool:0 Total Timed Out:0 The value of "Connections In Use Count" should be 8 in this case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira