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

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP 5.0.1
    • JCA
    • None
    • 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.
    • 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.

      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

          clones

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

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

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

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

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

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

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

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

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

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

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

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              jpederse@redhat.com Jesper Pedersen
              rhn-support-jbertram Justin Bertram
              Misty Stanley-Jones Misty Stanley-Jones (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: