I think this happens after a client has opened a socket connection to
the RabbitMQ broker, has sent the AMQP protocol header but has taken
too long to respond to the first AMQP command, i.e. ConnectionStart.
This could either because the network connection was too slow or got
interrupted or a client waited too long to start the AMQP connection
within the TCP connection it had already started.
To check for the first, you could run the client and the broker on the
same machine.
To check for the second, I would have to see your code to see if there
is a mistake anywhere. In general, the AS3 client sends a
ConnectionStartOk when the onStart() callback in the
ConnectionStateHandler is invoked. You can always set a breakpoint in
this method to find out whether it is being invoked or not.
Alternatively to test a more recent version of the AS3 client in a
really easy fashion to eliminate any problem there may be with the
current test code, you can use this demo client:
http://github.com/0x6e6562/json-over-amqp/ which will a simple client
out of the box.
Furthermore I do have a suite of unit tests that I use to develop the
client, which I haven't put into version control yet because it is in
a separate project because of the way Flexbuilder structures it's
projects. I could of course make this available.
HTH,
Ben