Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3882

No warning when a second LastResourceRecord is enlisted in a transaction

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.2.Final
    • 7.0.1.Final
    • Transaction Core
    • None
    • Hide

      Run test case com.hp.mwtests.ts.jta.lastresource.LastResourceDisallowTestCase and observe that there are no warnings when the second last resource is enlisted (the enlist fails by return boolean false but no indicate why it returned false).

      Show
      Run test case com.hp.mwtests.ts.jta.lastresource.LastResourceDisallowTestCase and observe that there are no warnings when the second last resource is enlisted (the enlist fails by return boolean false but no indicate why it returned false).
    • Hide

      Enable multiple last resources by setting CoreEnvironmentBean.allowMultipleLastResources to true (via the narayana config mechanisms).

      Show
      Enable multiple last resources by setting CoreEnvironmentBean.allowMultipleLastResources to true (via the narayana config mechanisms).
    • Low
    • Produces a warning if a second one phase aware resource is enlisted in a transaction.

      If CoreEnvironmentBean.allowMultipleLastResources is not enabled and if two last resources are enlisted in a transaction then the second enlistment fails because it is seen as a duplicate because all last LastResourceRecord's have the same uid. This is fine but there is no log message to indicate why the enlistment failed.

              rhn-engineering-mmusgrov Michael Musgrove
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: