Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-115

Repetitive reconnections when wrong password set

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.5.0, 0.6.0
    • Fix Version/s: 0.6.0
    • Component/s: qpid-jms-client
    • Labels:
    • Environment:

      Java 1.7

      Description

      When I supply wrong password in connection string, client tries connect again immediately after failure. These reconnection will happen until I stop the client.

      2015-09-22 12:36:08 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:08 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:09 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      2015-09-22 12:36:10 +0200 INFO org.apache.qpid.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-CRAM-MD5
      ...

      This is happening during creating session.

      session = connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);

      Used connection string:

      failover:(amqp://cbgc01:21415)?jms.username=admin&jms.password=admin2

      AMQP 0-10 client prints out an exception and quits when wrong password supplied, is same behavior expected here?

        Attachments

        1. unexistent.queue.log.txt
          227 kB
          Tomas Vavricka

          Activity

            People

            • Assignee:
              tabish Timothy A. Bish
              Reporter:
              vavrtom Tomas Vavricka
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: