Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1137

ClusterChooserInterceptor does not support transaction failover authorisations

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • AS 4.2.2.GA, AS 5.0.0.Beta3
    • Clustering
    • None

    Description

      org.jboss.aspects.remoting.ClusterChooserInterceptor does not contain logic to
      deal with transaction failover authorisations, contrary to legacy JRMP invoker or
      Unified invoker.

      The reason I'm entering this as a bug rather than as a feature request is because
      not having such logic is allowing failovers when they shouldn't happen.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users EJBTHREE-1141 LoadBalancePolicy that tries to pin all requests associated with a tx to one server

          • 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.
          • Resolved

          Feature Request - Feature requests from customers and/or users JBPAPP-5165 implement https://jira.jboss.org/browse/EJBTHREE-1137 in EAP

          • 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.
          • Resolved
          is incorporated by

          Sub-task - The sub-task of the issue JBPAPP-7015 Add EJB3 Transaction Stickiness Load Balancing Policies

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users JBAS-5239 Failover with a distributed transaction manager

          • 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

              pferraro@redhat.com Paul Ferraro
              rh-ee-galder Galder Zamarreño
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: