Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: JCA
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.1.0.GA
Steps to Reproduce:

Hide

tests from WildFly shows this (50%):
https://github.com/wildfly/wildfly/tree/master/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jca/capacitypolicies

Show
tests from WildFly shows this (50%): https://github.com/wildfly/wildfly/tree/master/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jca/capacitypolicies

SFDC Cases Counter:
SFDC Cases Links:

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

blocks

JBEAP-9840 Unignore XADatasourceCapacityPoliciesTestCase

Verified

clones

JBJCA-1344 race condition between PoolFiller and CapacityFiller results in wrong pool statistics

Closed

Assignee:: Martin Simka

Reporter:: Martin Simka

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2017/03/22 10:31 AM

Updated:: 2020/09/14 5:30 AM

Resolved:: 2017/04/18 5:39 AM