qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomas Vavricka (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (QPIDJMS-115) Repetitive reconnections when wrong password set
Date Wed, 23 Sep 2015 10:49:04 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904321#comment-14904321
] 

Tomas Vavricka edited comment on QPIDJMS-115 at 9/23/15 10:48 AM:
------------------------------------------------------------------

I can confirm that commit https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=2f97ccb
fixes the wrong password issue.

I encountered another issue maybe connected to this one.

Using properties:

{quote}
java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
connectionfactory.connection=failover:(amqp://cbgc01:21415?amqp.traceFrames=true)?jms.username=admin&jms.password=admin&failover.reconnectDelay=60000&failover.maxReconnectAttempts=2
queue.broadcastAddress2=nonexistent.queue
{quote}

When I try to create consumer

{{MessageConsumer broadcastConsumer = session.createConsumer((Destination) ctx.lookup("broadcastAddress2"));}}

exception is thrown, failover closes the connection and client tries to reconnect endlessly.

Logs are attached in file unexistent.queue.log.txt.


was (Author: vavrtom):
I can confirm that commit https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=2f97ccb
fixes the wrong password issue.

I encountered another issue maybe connected to this one.

Using properties:

{quote}
java.naming.factory.initial=org.apache.qpid.jms.jndi.JmsInitialContextFactory
connectionfactory.connection=failover:(amqp://cbgc01:21415?amqp.traceFrames=true)?jms.username=admin&jms.password=admin&failover.reconnectDelay=60000&failover.maxReconnectAttempts=2
queue.broadcastAddress2=nonexistent.queue
{quote}

When I try to create consumer

{{MessageConsumer broadcastConsumer = session.createConsumer((Destination) ctx.lookup("broadcastAddress2"));}}

exception is thrown, connection is closed and client tries to reconnect endlessly.

Logs are attached in file unexistent.queue.log.

> 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
>            Assignee: Timothy Bish
>              Labels: connection
>         Attachments: unexistent.queue.log.txt
>
>
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message