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

SFSB session open requests don't retry if a node is down

    XMLWordPrintable

Details

    Description

      This jira was created for tracking one of the aspects of https://issues.jboss.org/browse/JBEAP-12285, as agreed with Jason (https://issues.jboss.org/browse/JBEAP-12285?focusedCommentId=13466556&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13466556) because the original issue became too broad and covered multiple broken use cases.

      The problem is that if an EJB client specifies multiple PROVIDER_URL values, some of the servers aren't running, and the client tries to create a SFSB instance, it can happen that the request is load-balanced to the stopped server, fails, and is NOT reattempted on any other servers. This works fine for stateless beans.

      Attachments

        Issue Links

          is caused 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) EJBCLIENT-273 SFSB session open requests should retry

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-13264 Upgrade JBoss EJB Client to 4.0.2.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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12285 Remote EJB clustered node discovery is ignored

          • 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

              jgreene@redhat.com Jason Greene
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: