-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in amqp-0.5
#17
Comments
I think it might be the call to |
Your intuition was right: the |
According to the documentation 0 should only be returned on EOF. Can we rule out that the socket has been closed? You may want to look at the RabbitMQ log file. |
Yes, there is an error in the RabbitMQ log file each time this happens:
I also forgot to mention that there was in fact a long delay before the exception occurred (~10 seconds, as you can see from the log). When I use |
That's very strange. You may want to add some print statements to |
The most likely explanation is that we need to call |
It may be necessary to use @Gabriel439 the error message means that RabbitMQ did not receive initial protocol handshake (which is 7 bytes, |
I will do that. Just give me until Thursday as I'm busy through tomorrow. |
FWIW, I can reproduce the exception by supplying a non-existing user/password combination. Sticking closed <- hIsEOF handle
when closed $ error "connection is closed" at the start of |
I added some calls to |
Hm, just to be sure, I did a couple of runs with and without the call to Looking at the server log, the connection is obviously properly closed with the wrong, compared to @Gabriel439's |
In any case, I think it'd be better if a closed connection wouldn't manifest in error at |
I agree. The exception handling needs a lot of improvement. |
When I upgrade my code from 0.4.2 to 0.5 I get the following mysterious error when connecting to a message queue:
I'm limited for time at the moment, so I haven't had time to narrow down this test case from within the application that this occurred in, but my best guess from studying the diff between 0.4.2 and 0.5 is that this exception probably originated in your internal
readFrame
function.The text was updated successfully, but these errors were encountered: