You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/08/26 17:30:50 UTC

[jira] [Commented] (AMQ-5948) connection.start hangs with tcp transport wrong username / password

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

Timothy Bish commented on AMQ-5948:
-----------------------------------

Would surprise me that this is the case given that we have tests for this very scenario.  I'd recommend you create a unit test that encapsulates your broker and client configuration to reproduce the problem.  

> connection.start hangs with tcp transport wrong username / password
> -------------------------------------------------------------------
>
>                 Key: AMQ-5948
>                 URL: https://issues.apache.org/jira/browse/AMQ-5948
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.12.0
>            Reporter: Antonio Castaldo D'Ursi
>
> Hi,
> I am trying to connect to an ActiveMq Broker version 5.11.1 , using the ActiveMQConnectionFactory. On the client side I tried both client version 5.11.2 and 5.12.0
> On server side, authentication is enabled.
> If I supply wrong username and password, the call to connection.start() hangs .
> Debugging the code, I see it hangs in org.apache.activemq.transport.FutureResponse.getResult().
> (this is indirectly called by syncSendPacket in the ensureConnectionInfoSent method in ActiveMQConnectionFactory)
> On server side, i see the error message:
>  INFO | Stopping tcp://127.0.0.1:53846 because Failed with SecurityException: User name [null] or password is invalid.
> It looks like client side is waiting indefinitely for an answer that will never arrive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)