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.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.1
    • EAP_EWP 5.1.0
    • JCA
    • None

    • Linux, JBoss EAP 5.1

    • Release Notes
    • 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.
    • Not Yet Documented

      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

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

            rhn-support-toross Tom Ross
            rhn-support-toross Tom Ross
            Misty Stanley-Jones Misty Stanley-Jones (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: