Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8427

Unignore XADatasourceCapacityPoliciesTestCase

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 11.0.0.Beta1
    • Component/s: None
    • Labels:
      None

      Description

      I am going to ignore this test, until the ironjacamar upgrade which fixes the following (from Martin Simka's mail)

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  simkam Martin Simka
                  Reporter:
                  kabirkhan Kabir Khan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: