Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5596

Incorrect handling of multi-threaded access to JCA connections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP 5.0.1
    • Fix Version/s: EAP_EWP 5.1.1
    • Component/s: JCA
    • Labels:
      None
    • Release Notes Text:
      Hide
      The JCA code did not properly handle multi-threaded access, due to several potential causes of deadlocks involving JDBC operations and the JBossTS transaction reaper thread. The JCA code has been updated to resolve these problems, and multi-threaded access should work properly in the JCA.
      Show
      The JCA code did not properly handle multi-threaded access, due to several potential causes of deadlocks involving JDBC operations and the JBossTS transaction reaper thread. The JCA code has been updated to resolve these problems, and multi-threaded access should work properly in the JCA.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      The attached dumps contain 4 dead-locks involving JCA (i.e. JDBC operations) and the JBossTS transaction reaper thread. It appears that the JCA code is not properly handling multi-threaded access properly resulting in a dead-lock.

        Gliffy Diagrams

          Attachments

          1. console1.out
            325 kB
          2. console2.out
            285 kB
          3. jca-deadlock.zip
            1.43 MB
          4. server1.log
            7.73 MB
          5. server2.log
            8.16 MB
          6. stack
            6 kB
          7. twiddle-stack
            7 kB
          8. WrappedConnection.java.diff
            0.7 kB

            Issue Links

            blocks

            Bug - A problem which impairs or prevents the functions of the product. SOA-2701 Potential for dead-lock in JCA layer when JBossTS transaction reaper aborts a transaction

            • Blocker - An issue (bug, feature, task) that blocks development and/or testing work, production could not run. An upcoming version that is affected by this issue cannot be released until it's addressed.
            • Closed
            cloned to

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-6410 CLONE - Incorrect handling of multi-threaded access to JCA connections

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed
            is incorporated by

            Support Patch - A one-off patch related to a customer support case JBPAPP-5697 Backport JBPAPP-5596: Incorrect handling of multi-threaded access to JCA connections

            • Major - A request that should be considered seriously but is not a show stopper.
            • Resolved

            Support Patch - A one-off patch related to a customer support case JBPAPP-5698 Backport JBPAPP-5596: Incorrect handling of multi-threaded access to JCA connections

            • Major - A request that should be considered seriously but is not a show stopper.
            • Resolved
            is related to

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-662 Need to check transaction status on SQL operations

            • Major - A request that should be considered seriously but is not a show stopper.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JBAS-5095 Race condition between connection.close() and transaction.rollback() causes connection leak

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-6684 Deadlock in JCA when TM tries to commit/rollback

            • Blocker - An issue (bug, feature, task) that blocks development and/or testing work, production could not run. An upcoming version that is affected by this issue cannot be released until it's addressed.
            • Closed

              Activity

                People

                • Assignee:
                  jesper.pedersen Jesper Pedersen
                  Reporter:
                  jbertram Justin Bertram
                  Writer:
                  Misty Stanley-Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: