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

During XA recovery JCA code does not check if the database connection it is using is valid.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0
    • Fix Version/s: EAP_EWP 5.1.1
    • Component/s: JCA
    • Labels:
      None
    • Environment:

      Linux, JBoss EAP 5.1

    • Affects:
      Release Notes
    • Release Notes Text:
      During the recovery of a failed XA transaction involving a JDBC <xa-datasource> the JCA adaptor would use a cached JDBC connection without checking if it was still valid sometimes resulting in an XAException.
    • Release Notes Docs Status:
      Not Yet Documented

      Description

      During XA recover JCA adaptor is trying to use a cached handle to last connection used without checking if it is still a valid connection. This results in XAException

      [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException, XAException.XAER_RMERR

      when the recover module is trying to use it.

      See
      http://community.jboss.org/thread/92291?start=70&tstart=0

        Gliffy Diagrams

          Attachments

          1. JBPAPP-5292.patch
            2 kB
          2. JBPAPP-5292.patch
            9 kB
          3. JBPAPP-5292.patch
            5 kB
          4. JBPAPP-5292.patch
            3 kB

            Issue Links

              Activity

                People

                • Assignee:
                  raggz Tom Ross
                  Reporter:
                  raggz Tom Ross
                  Writer:
                  Misty Stanley-Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: