Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7084

Add support for a traditional XA strategy in the JMS resource adapter

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 6.0.0.M1
    • None
    • JCA service
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration
    • 0
    • 0% 0%

    Description

      Add support for a traditional (JCA 1.5 Chapter 12.5.6 Option A) XA transaction model in the generic JMS resource adapter.

      The default when using an XASession should be the traditional one, but the old behavior can be enabled by setting the ForceTransacted flag in the activation spec.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-2260 Setting maxMessages > 1 results in multiple message deliveries within one transaction

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jpederse@redhat.com Jesper Pedersen
              jpederse@redhat.com Jesper Pedersen
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: