[jboss-jira] [JBoss JIRA] (WFLY-8427) Unignore XADatasourceCapacityPoliciesTestCase

[Martin Simka (JIRA)]

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

Martin Simka updated WFLY-8427:
-------------------------------
    Git Pull Request: https://github.com/wildfly/wildfly/pull/9941


> Unignore XADatasourceCapacityPoliciesTestCase
> ---------------------------------------------
>
>                 Key: WFLY-8427
>                 URL: https://issues.jboss.org/browse/WFLY-8427
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Kabir Khan
>            Assignee: Martin Simka
>
> I am going to ignore this test, until the ironjacamar upgrade which fixes the following (from [~simkam]'s mail)
> {quote}
> I might be completely wrong, but it seems to me like race condition between PoolFiller and CapacityFiller in IronJacamar. 
> 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 https://github.com/ironjacamar/ironjacamar/blob/1.4/core/src/main/java/org/jboss/jca/core/connectionmanager/pool/mcp/SemaphoreConcurrentLinkedDequeManagedConnectionPool.java#L1163
> @Stefano, @Flavia could you please take a look? 
> I'm attaching logs with enabled TRACE on org.jboss.jca and jdbc.spy. 
> This might have been hidden until https://issues.jboss.org/browse/JBJCA-1330 was fixed in DR11.
> {quote}



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