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

[QA](7.2.z) Shutdown of server with remote JCA MDB hangs

    XMLWordPrintable

Details

    Description

      We have following scenario:

      • 2 EAP instances (nodeA, nodeB)
      • nodeB has a MDB deployed, that consumes messages from an InQueue on nodeA and resends them to an OutQueue also on nodeA
      • during the MDB processing of messages, nodeA is killed (actually killed, not a clean shutdown)

      After that nodeB hangs when trying to shut it down and has to be killed.
      This is a regression against 7.2.3.CR2 with Artemis 2.7.0.redhat-00057

      Attachments

        Issue Links

          blocks

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17062 [GSS](7.2.z) Upgrade Artemis from 2.7.0.redhat-00057 to 2.9.0.redhat-00005

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2720 Connection Timeout now blocks on the retry, it should be asynchronous

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17062 [GSS](7.2.z) Upgrade Artemis from 2.7.0.redhat-00057 to 2.9.0.redhat-00005

          • 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
          links to

          Web Link ARTEMIS-2440

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              pmackay@redhat.com Peter Mackay
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: