[jira] [Updated] (QPID-5438) Connecting to qpid-cpp with SASL2 hangs

["Rob Godfrey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey updated QPID-5438:
------------------------------
    Summary: Connecting to qpid-cpp with SASL2 hangs  (was: [AMQP 1.0 JMS client] Connecting to qpid-cpp with SASL2 hangs)

> Connecting to qpid-cpp with SASL2 hangs
> ---------------------------------------
>
>                 Key: QPID-5438
>                 URL: https://issues.apache.org/jira/browse/QPID-5438
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker
>    Affects Versions: 0.27
>         Environment: qpid-cpp 0.27 (from trunk), qpid-amqp-1-0-client-jms-0.28-SNAPSHOT (from trunk). Broker running on CentOS 6..0, client running on Linuxmint 15
>            Reporter: Ulrich Romahn
>            Priority: Critical
>
> I have SASL2 enabled on the broker with the correct configuration.
> When connecting to the broker from the Java client using the following URL amqp://guest:guest@qpid-cpp-server:5672 I am getting an error message on the broker, saying that no protocol was sent and it will close the connection. This will cause the client to hang while trying to connect.
> I suspect the client will eventually get a timeout exception, but I never waited that long. The same connection succeeds on the Java Broker v 0.24.



--
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