Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-633

auto-enlisting JDBC drivers in Aries transaction manager is broken

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.1
    • fuse-esb-7.1.0
    • None
    • None
    • % %

      As per doc at https://access.redhat.com/knowledge/docs/en-US/Fuse_ESB_Enterprise/7.1/html/EIP_Transaction_Guide/files/XaJdbc-AutoEnlist.html, JDBC drivers get auto-enlisted in the Aries Transaction Manager. This process however is currently broken.

      • There is a problem with the underlying pooling, it can result in an error similar to 
          Pool empty. Unable to fetch a connection in 30 seconds

        after processing a few messages.

      • The enlisted XA wrapper driver is XA aware but does not implement Geronimo's NamedXAResource interface and hence writing the transaction log file fails with an error like 
          java.lang.IllegalStateException: Cannot log transactions as org.apache.derby.client.net.NetXAResource@36e8b592 is not a NamedXAResource.

      As a result the Aries auto-enlisting XA wrappers cannot be used atm.

              g_nodet Guillaume Nodet (Inactive)
              rhn-support-tmielke Torsten Mielke
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: