qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Giusti (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QPID-5789) Cannot connect to broker if max-negotiate-time is set to zero
Date Tue, 27 May 2014 15:17:02 GMT
Ken Giusti created QPID-5789:
--------------------------------

             Summary: Cannot connect to broker if max-negotiate-time is set to zero
                 Key: QPID-5789
                 URL: https://issues.apache.org/jira/browse/QPID-5789
             Project: Qpid
          Issue Type: Bug
          Components: C++ Broker
    Affects Versions: 0.28
            Reporter: Ken Giusti
            Priority: Trivial
             Fix For: 0.29


The broker accepts zero (0) as a valid setting for the max-negotiation-time configuration
parameter.  However, setting this to zero prevents clients from connecting.

A "more-sane" lower bound should be set for this parameter, or at least a warning should be
issued if set to zero.

$ qpidd --max-negotiate-time 0 --auth no
2014-05-27 11:10:22 [Security] notice SSL plugin not enabled, you must set --ssl-cert-db to
enable it.
2014-05-27 11:10:22 [Broker] notice SASL disabled: No Authentication Performed
2014-05-27 11:10:22 [Network] notice Listening on TCP/TCP6 port 5672
2014-05-27 11:10:22 [Broker] notice Broker running
2014-05-27 11:10:37 [System] error Connection qpid.[::1]:5672-[::1]:34525 No protocol received
closing
2014-05-27 11:10:56 [System] error Connection qpid.[::1]:5672-[::1]:34529 No protocol received
closing

Both failures occurred as a result of trying to run 'qpid-config'





--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message