You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "michael j. goulish (Created) (JIRA)" <ji...@apache.org> on 2012/01/24 14:58:42 UTC
[jira] [Created] (QPID-3778) qpid-stat with MD5 fails when other
tools running
qpid-stat with MD5 fails when other tools running
-------------------------------------------------
Key: QPID-3778
URL: https://issues.apache.org/jira/browse/QPID-3778
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Reporter: michael j. goulish
Assignee: michael j. goulish
qpid-stat reliably fails with a "connection aborted" message when it is connected through SASL MD5, and when there are several qpid-tools also connected to the broker.
The qpid-tools do not have to be connected with MD5. They do not have to be doing anything, just sitting there.
In my testing the qpid-stat failure occurred close to 100% of the time when there were at least 3 qpid-tools connected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3778) qpid-stat with MD5 fails when other
tools running
Posted by "michael j. goulish (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
michael j. goulish resolved QPID-3778.
--------------------------------------
Resolution: Fixed
Fix Version/s: 0.14
fixed in rev 1235255
It is OK for call to sasl_decode() to return 0-length data, as long as result code is SASL_OK. This just means that the next call will give you some data.
We were treating this an an error, and throwing a spurious exception that made us (um, 'us' meaning 'me') believe that it was the SASL handshake that was failing.
> qpid-stat with MD5 fails when other tools running
> -------------------------------------------------
>
> Key: QPID-3778
> URL: https://issues.apache.org/jira/browse/QPID-3778
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Reporter: michael j. goulish
> Assignee: michael j. goulish
> Fix For: 0.14
>
>
> qpid-stat reliably fails with a "connection aborted" message when it is connected through SASL MD5, and when there are several qpid-tools also connected to the broker.
> The qpid-tools do not have to be connected with MD5. They do not have to be doing anything, just sitting there.
> In my testing the qpid-stat failure occurred close to 100% of the time when there were at least 3 qpid-tools connected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org