[jboss-jira] [JBoss JIRA] (JBJCA-951) The pool statistics "Available" shows wrong value after fill pool

[Jesper Pedersen (JIRA)]

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

Jesper Pedersen resolved JBJCA-951.
-----------------------------------

    Resolution: Done

    
> The pool statistics "Available" shows wrong value after fill pool
> -----------------------------------------------------------------
>
>                 Key: JBJCA-951
>                 URL: https://issues.jboss.org/browse/JBJCA-951
>             Project: IronJacamar
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.14.Final, 1.1.0.Beta3
>            Reporter: Masafumi Miura
>            Assignee: Jesper Pedersen
>             Fix For: 1.0.15.Final, 1.1.0.Beta4
>
>
> The pool statistics' "Available" shows wrong value (one less than "max-pool-size") after fill pool.
> For example, min-pool-size=5, max-pool-size=10 and prefill=true are set to datasource configuration: 
> {code:xml}
>   <pool>
>       <min-pool-size>5</min-pool-size>
>       <max-pool-size>10</max-pool-size>
>       <prefill>true</prefill>
>   </pool>
> {code}
> Then, when checking pool stats via CLI after JBoss start-up, the results shows the following:
> {code}
> [standalone at localhost:9999 /] /subsystem=datasources/data-source=ExampleDS/statistics=pool/:read-resource(recursive=false,proxies=false,include-runtime=true,include-defaults=true) 
> {
>     "outcome" => "success",
>     "result" => {
>         "ActiveCount" => "5",
>         "AvailableCount" => "9",
>         "AverageBlockingTime" => "0",
>         "AverageCreationTime" => "3",
>         "CreatedCount" => "5",
>         "DestroyedCount" => "0",
>         "MaxCreationTime" => "4",
>         "MaxUsedCount" => "1",
>         "MaxWaitTime" => "0",
>         "TimedOut" => "0",
>         "TotalBlockingTime" => "0",
>         "TotalCreationTime" => "17"
>     }
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira