On 05/25/2012 03:59 PM, Andrew Stitcher wrote:
On Thu, 2012-05-24 at 08:59 +0100, Keith W wrote:
Hello
The Qpid-Python-Cpp-Test started to fail on May 21st. Many tests are
failing and others are begin skipped. I turned on DEBUG logging from the
Python tests, and logging from the CPP Broker, but it is no obvious to me
what has gone wrong. The Python/Java tests continue to pass.
...
The Broker is logging only:
2012-05-24 04:08:11 notice SASL disabled: No Authentication Performed
2012-05-24 04:08:11 notice Listening on TCP/TCP6 port 35672
2012-05-24 04:08:11 notice Broker running
2012-05-24 04:08:13 error Execution exception: not-allowed: Exchange
declared with alternate-exchange<nonexistent>, requested alt1
(qpid/broker/SessionAdapter.cpp:133)
2012-05-24 04:08:14 error Connection 127.0.0.1:35672-127.0.0.1:44003
No protocol received closing
This message comes from the recent "DoS prevention code" (well badly
behaved client code prevention really) - If a client has not sent the
initial "AMQP" + version bytes within a reasonable time (2s by default)
a connection is closed peremptorily.
FWIW I really don't like that code.
It doesn't actually protect from badly behaved client code anyway, only
from one specific case. Provided you send a valid AMQP header you can
still use up all the connections without doing anything further and
without authenticating.
Rather than having a maximum time to negotiate the protocol version what
is really needed is a maximum time to authenticate.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
