[
https://issues.apache.org/jira/browse/QPIDJMS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902624#comment-14902624
]
Timothy Bish commented on QPIDJMS-115:
--------------------------------------
We need a bit more info before we can really determine what happened here.
Details like what broker (and its version) you are using would be great to
provide. If you have the resources to capture the AMQP / SASL frames that are
exchanged during the connection attempt that would also provide much needed
insight into what transpired.
> Repetitive reconnections when wrong password set
> ------------------------------------------------
>
> Key: QPIDJMS-115
> URL: https://issues.apache.org/jira/browse/QPIDJMS-115
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.5.0, 0.6.0
> Environment: Java 1.7
> Reporter: Tomas Vavricka
> Labels: connection
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
