[
https://jira.jboss.org/jira/browse/JBAS-6819?page=com.atlassian.jira.plug...
]
Farah Juma commented on JBAS-6819:
----------------------------------
Our test in the EMBJOPR testsuite is still failing. It looks like the assertions in the
test in the AS testsuite are different from the assertions in our test.
The test in the EMBJOPR testsuite asserts that the metric values are correct after closing
some, but not all, connections.
However, the first couple of assertions in the test in the AS testsuite verify that the
metric values are correct after creating multiple connections. These assertions are
similar to another one of our tests in the EMBJOPR testsuite -
testListFormattedSubPoolStatisticsAfterMultipleConnections. Next, the test in the AS
testsuite closes all connections, flushes the connection pool, and then verifies the
metric values are correct after the flush operation is performed. This is similar to
another one of our tests in the EMBJOPR testsuite -
testFlushOperationAfterMultipleConnections. Both of these EMBJOPR tests have been passing
in my local runs (these tests should pass on Hudson as well once we get a successful run
that includes the changes that were made to the tests to match the new layout for the ops
page).
The value of "Connections In Use Count" that gets displayed
in the embedded console as the result of the "List Formatted Sub Pool
Statistics" operation does not get updated after connections are closed
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6819
URL:
https://jira.jboss.org/jira/browse/JBAS-6819
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: ProfileService
Environment: JBoss Branch_5_x r85739, embjopr r209
Reporter: Farah Juma
Assignee: Farah Juma
Priority: Critical
Fix For: JBossAS-5.1.0.GA
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