Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-289

Retry race condition in sendRequestInitial

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 4.0.8.Final
    • None
    • None

    Description

      In the rare case that a worker thread notifying failure on an initial request beats the initial request (e.g. due to a yield from thread scheduling), the interceptor stack is never utilized, and thus a retry is never requested.

      This can lead to intermittent loss of failover behavior in a load-balanced/clustered configuration.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13606 EJB client: Retry functionality in HA scenarios intermittently breaks

          • 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-13630 Upgrade ejb-client to 4.0.8.Final

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

          Activity

            People

              jgreene@redhat.com Jason Greene
              jgreene@redhat.com Jason Greene
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: