Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-12

AMQP 1.0 jms client hangs when another reconnect should happen on the same MRGM broker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • qpid-jms
    • Compatibility/Configuration, User Experience
    • Hide

      1) Keep starting and stopping MRG-M broker
      $ while true; do service qpidd start; sleep 3; service qpidd stop; done;

      2) Create queue
      $ qpid-config add queue test_reconnect_tx_rx
      3) Send few durable messages with enabled reconnect while qpidd broker is being started & stopped in a loop.
      $ ./aac1_sender.java.sh --timeout 120 --broker failover:amqp://localhost:5672 --duration 20 --count 20 --log-msgs dict -a "test_reconnect_tx_rx" --conn-username guest --conn-password guest --conn-reconnect-backoff false --conn-reconnect-limit -1

      <see attached qpid-jms-client-reconnect.log>

      Client is able to send few messages again (so it reconnects once), but then it fails to reconnect again and hangs.

      I am attaching another log of both qpid-java & qpid-jms client.

      Show
      1) Keep starting and stopping MRG-M broker $ while true; do service qpidd start; sleep 3; service qpidd stop; done; 2) Create queue $ qpid-config add queue test_reconnect_tx_rx 3) Send few durable messages with enabled reconnect while qpidd broker is being started & stopped in a loop. $ ./aac1_sender.java.sh --timeout 120 --broker failover:amqp://localhost:5672 --duration 20 --count 20 --log-msgs dict -a "test_reconnect_tx_rx" --conn-username guest --conn-password guest --conn-reconnect-backoff false --conn-reconnect-limit -1 <see attached qpid-jms-client-reconnect.log> Client is able to send few messages again (so it reconnects once), but then it fails to reconnect again and hangs. I am attaching another log of both qpid-java & qpid-jms client.

      Client hangs in a second and subsequent failover reconnect attempt on the same MRG-M broker, with "Transport connection remotely closed". No error is reported and client keeps running.

              gemmellr Robbie Gemmell
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: