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

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major 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

      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.

        1. console1.out
          325 kB
          Justin Bertram
        2. console2.out
          285 kB
          Justin Bertram
        4. server1.log
          7.73 MB
          Justin Bertram
        5. server2.log
          8.16 MB
          Justin Bertram
        6. stack
          6 kB
          Kevin Conner
        7. twiddle-stack
          7 kB
          Kevin Conner
        8. WrappedConnection.java.diff
          0.7 kB
          Kevin Conner

              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

                Created:
                Updated:
                Resolved: