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

EJB client 4.x occasionally hangs

    XMLWordPrintable

Details

    Description

      As mentioned in https://issues.jboss.org/browse/JBEAP-12074?focusedCommentId=13463390&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13463390

      Some of the standalone EJB clients gets stuck shortly after the test begins.

      Scenario description: 4 node cluster with a clustered EJB application deployed on each server, one node at time is shut down gracefully/killed, while 2000 standalone EJB clients keep calling the application.

      Please see the comments after that for some background information, but for the continuation use this issue

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12074 EJB client 4.x freezes intermittently after some time

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13345 Remoting messages might not be processed in some edge cases

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

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-267 Invalid state possible in getResult

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

          Bug - A problem that impairs or prevents the functions of the product. REM3-307 IntIndexHashMap.get() can return null when the map is being resized

          • 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-13373 Upgrade remoting to 5.0.3.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

              sdouglas1@redhat.com Stuart Douglas
              mvinkler1@redhat.com Michal Vinkler
              Daniel Cihak Daniel Cihak
              Daniel Cihak Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: