Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3114

Qpid JMS client doesn't recover after a complete outage

    XMLWordPrintable

Details

    • Release Notes
    • +
    • Hide
      Previously, if a master-slave broker pair failed back to the original master broker following an outage, a Qpid JMS client could not reconnect to the master. This failed connection was caused by failure of the broker to remove its existing client IDs following failback. This issue is now resolved.
      Show
      Previously, if a master-slave broker pair failed back to the original master broker following an outage, a Qpid JMS client could not reconnect to the master. This failed connection was caused by failure of the broker to remove its existing client IDs following failback. This issue is now resolved.
    • Documented as Resolved Issue
    • Verified in a release

    Description

      When qpid jms client is connected to broker using failover, after a complete outage (e.g. full bounce) the qpid jms client doesn't recover.
      The business impact is that all clients have to be bounced after a broker outage, this causes significant delay in recovering service after a broker outage, as restarting 100's of apps and instances is not a small task.

      Customer is a upstream committer and fixed the issue on this JIRA:
      https://issues.apache.org/jira/browse/ARTEMIS-2547

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3069 Qpid JMS client doesn't recover after a complete outage

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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3264 broker rejects reconnect on broker stop/start

          • 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

          Activity

            People

              rh-ee-ataylor Andy Taylor
              dbruscin Domenico Francesco Bruscino
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: