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

broker rejects reconnect on broker stop/start

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.4.3.CR1
    • None
    • None
    • None
    • +
    • Hide
      Previously, if a broker was stopped and restarted, an AMQP client (for example, an AMQ JMS client) with reconnect logic could not reconnect to the broker. Specifically, the broker rejected the connection, indicating that the client ID already existed. This issue is now resolved.
      Show
      Previously, if a broker was stopped and restarted, an AMQP client (for example, an AMQ JMS client) with reconnect logic could not reconnect to the broker. Specifically, the broker rejected the connection, indicating that the client ID already existed. This issue is now resolved.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      See attached project

      Prerequisites:

      • master/slave broker pair
      • edit class QpidJMSPubClientIDFailoverIssue for broker URLs

      Test 1:

      mvn clean install
java -jar target/failover-clientid-1.0.0-SNAPSHOT.jar

      kill/stop broker (sometimes required more than once), the client does not failover to the new broker

      Show
      See attached project Prerequisites: master/slave broker pair edit class QpidJMSPubClientIDFailoverIssue for broker URLs Test 1: mvn clean install java -jar target/failover-clientid-1.0.0-SNAPSHOT.jar kill/stop broker (sometimes required more than once), the client does not failover to the new broker

    Description

      On reconnect with QPID JMS, it is sometimes seen that the broker rejects the connection, indicating the attempt failed due to the ClientID already being in use when it is not.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3215 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
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3114 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

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-shiggs Stephen Higgs
              Tiago Bueno Tiago Bueno
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: