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

broker rejects reconnect on broker stop/start

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major 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

      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.

        1. ENTMQCL-1952-client-failover-output.txt
          226 kB
        2. failoverclientid-1.0.0-SNAPSHOT.tar.gz
          2 kB

              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

                Created:
                Updated:
                Resolved: