Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6609

STOMP netty connector failing when a messaging cluster node drops out.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 12.0.0.Final
    • 10.0.0.Final
    • JMS
    • None
    • Hide
      1. Create multiple wildfly instances and configure clustered messaging
      2. Configure the connector to allow for STOMP connections
      3. Add a queue
      4. Create a client that uses STOMP to send/receive messages
      5. Terminate the wildfly instance the client is not connecting to
      6. Messaging over STOMP will no longer work
      Show
      Create multiple wildfly instances and configure clustered messaging Configure the connector to allow for STOMP connections Add a queue Create a client that uses STOMP to send/receive messages Terminate the wildfly instance the client is not connecting to Messaging over STOMP will no longer work

    Description

      If a client uses STOMP to publish or subscribe to the messaging server the client will cease to function when a messaging server node drops out of the cluster. They will only work again once the cluster has been fully terminated and at least one instance is brought back online.

      The error I received when sending messages:

      "AMQ339001: Destination does not exist: <queue_name>"

      lead me to a bug report ARTEMIS-358

      I built an Artemis 1.3 snapshot and the problem has been solved. I don't know if that particular bug was the cause but they have addressed the issue in an upcoming version of Artemis.

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-6730 Upgrade Artemis 1.3.0

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

          ARTEMIS-358 Loading...

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              chris_orser Chris Orser (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: