[jboss-jira] [JBoss JIRA] (JBJCA-1344) race condition between PoolFiller and CapacityFiller results in wrong pool statistics

[Flavia Rainone (JIRA)]

    [ https://issues.jboss.org/browse/JBJCA-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13388183#comment-13388183 ] 

Flavia Rainone commented on JBJCA-1344:
---------------------------------------

As a side note,, I used the IronJacamar tracer, as [~maeste] adivsed, to track this bug, and I ended up finding a problem in the trace result, there are some unexpected clearConnectionListener invocations flagged as Red. I'm investigating what is causing that trace result, if this is a known issue, please let me know.

> race condition between PoolFiller and CapacityFiller results in wrong pool statistics
> -------------------------------------------------------------------------------------
>
>                 Key: JBJCA-1344
>                 URL: https://issues.jboss.org/browse/JBJCA-1344
>             Project: IronJacamar
>          Issue Type: Bug
>    Affects Versions: 	 WildFly/IronJacamar 1.4.2.Final
>            Reporter: Martin Simka
>            Assignee: Flavia Rainone
>         Attachments: fail.log, pass.log
>
>
> There seems to be race condition between PoolFiller and CapacityFiller which results in wrong pool statistics
> I think what happens is:
>  - Both add connections to pool in different threads
>  - PoolFiller creates connection, then checks pools size and because pool has already certain size, it doesn't add connection and instead it destroys connection which increases destroyedCount
> see [SemaphoreConcurrentLinkedDequeManagedConnectionPool.java#L1163|https://github.com/ironjacamar/ironjacamar/blob/1.4/core/src/main/java/org/jboss/jca/core/connectionmanager/pool/mcp/SemaphoreConcurrentLinkedDequeManagedConnectionPool.java#L1163]



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)