[embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-71) AS5 plugin: Datasource metrics are not updated after a connection is requested from a connection pool

[Charles Crouch (JIRA)]

     [ https://jira.jboss.org/jira/browse/EMBJOPR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Crouch updated EMBJOPR-71:
----------------------------------

    Priority: Critical  (was: Major)


> AS5 plugin: Datasource metrics are not updated after a connection is requested from a connection pool
> -----------------------------------------------------------------------------------------------------
>
>                 Key: EMBJOPR-71
>                 URL: https://jira.jboss.org/jira/browse/EMBJOPR-71
>             Project: Embedded Jopr
>          Issue Type: Bug
>          Components: Web App/Integration
>         Environment: JBoss AS Branch_5_x r83903, embjopr r138
>            Reporter: Farah Juma
>            Priority: Critical
>             Fix For: 1.2
>
>
> Steps to reproduce when the console is deployed to JBoss AS Branch_5_x:
> Create a new -ds.xml file. Set values for min-pool-size and max-pool-size. After a connection is requested from the connection pool, check the metric values. These values are not updated. These values also remain unchanged after refreshing the page.
> For example, the following are the metric values that get displayed after the first request for a connection is made when the minimum pool size is 5 and the maximum pool size is 20:
> Available Connection Count: 20.0
> Connection Count: 0.0
> Connection Created Count: 0.0
> Connection Destroyed Count: 0.0
> In Use Connection Count: 0.0
> Max Connections In Use Count: 0.0
> Max Size: 20.0
> Min Size: 5.0 

-- 
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