[rabbitmq-discuss] Rabbitmq 2.5-2.6.1 java hanging on close of connection

Benjamin Bennett benbennett at gmail.com
Wed Nov 2 16:07:30 GMT 2011


I have am trying to figure out what is going on and I have tried many
different combinations.
The stack trace is the same as mentioned in this discussion
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-August/014790.html
 .
I am running unit level test cases for the project I am working on and
the test cases just hang unless I kill the build.
For the   windows 7 32 bit fdcc 3.1 (US Gov standard load) load
running in vsphere 4.1.X , it hangs 90% of the time .
For my Ubuntu 64-bit 11.04 box.(on bare metal no vmware)   it rarely
hangs but I just kicked of the build and it hung all night and I had
to kill it.
I have tried switching the jre(1.6.u26 , 1.6u29) , rabbitmq java
client (2.3.1,2.5.0,2.6.1), rabbitmq(2.5.0,2.5.1,2.6.0,2.6.1), erlang
R14B03 , R14B04.

I mixed and matched all the versions pretty much and the same thing
happens almost every single time on the windows 7 32 box

I used the Tracer tool and the tests cases don't hang but the
following exception is sometimes thrown.

1320191848535: <Tracer-3> ch#2 <- {#method<channel.close-ok>(),null,""}
1320191848535: <Tracer-3> ch#0 ->
{#method<connection.close>(reply-code=200, reply-text=OK, class-id=0,
method-id=0),null,""}
1320191848535: <Tracer-3> ch#0 <- {#method<connection.close-ok>(),null,""}
1320191848535: <Tracer-3> uncaught java.io.EOFException
        at java.io.DataInputStream.readUnsignedByte(Unknown Source)
        at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:99)
        at com.rabbitmq.tools.Tracer$DirectionHandler.readFrame(Tracer.java:271)
        at com.rabbitmq.tools.Tracer$DirectionHandler.doFrame(Tracer.java:305)
        at com.rabbitmq.tools.Tracer$DirectionHandler.run(Tracer.java:345)
        at java.lang.Thread.run(Unknown Source)

The entire tracer log is here http://pastebin.com/ecp9ymsH  .

I am pretty sure this is causing the hang but how can catch this
exception on the connection close method and not deadlock.


Thanks,
Benjamin Bennett


More information about the rabbitmq-discuss mailing list