Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13364

EJB over HTTP always fails with UserTransaction usage

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Blocker
    • 7.1.0.CR3
    • 7.1.0.CR2
    • EJB
    • None

    Description

      With the introduction of Lazy UT in CR2 (JBEAP-12998) HTTP UT support was broken, however this went undetected by the testsuite due to another bug (EJBCLIENT-247) that covered up the failure by rerouting the proxy over standard the standard remoting protocol, thereby causing the tests to verify remoting behavior as opposed to HTTP behavior. EJBCLIENT-247 was superseded by JBEAP-13343

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WEJBHTTP-5 Transaction location is never set with RemoteUT

          • 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 caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12998 [GSS](7.1.0) UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-247 EJB client allows failover of an EJB invocation with an active client transaction obtained via legacy EJBClient method

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-13343 [GSS] JTA based transaction stickiness

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-13363 Upgrade WildFly HTTP client components to 1.0.4.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              dlloyd@redhat.com David Lloyd
              jgreene@redhat.com Jason Greene
              Jan Martiska Jan Martiska
              Jan Martiska Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: