Details

    • Sub-task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • EAP_EWP 5.1.2
    • EAP_EWP 5.2.0
    • HornetQ
    • None
    • Release Notes
    • Hide
      An issue was identified in which it was possible to have duplicate resource recovery entries for one recovery manager, resulting in recovery scans conflicting with each other. This problem has been resolved by implementing auto-discovery of resources instead of manual configuration.
      Show
      An issue was identified in which it was possible to have duplicate resource recovery entries for one recovery manager, resulting in recovery scans conflicting with each other. This problem has been resolved by implementing auto-discovery of resources instead of manual configuration.
    • Documented as Resolved Issue
    • NEW

    Description

      There are a few cases where we could avoid duplicate entries on the Resource adapters. Like having different Connection factories among different resource adapters that are going towards the same server.

      There are still a few cases where we are going to improve on the next release, so at this time users will also need to deploy fixes from JBTM-842.

      We were told that would be ok to return XIDs from different resources but that was clearly not true as this fired an issue on the TM.

      Attachments

        Issue Links

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              csuconic@redhat.com Clebert Suconic
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: