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

[Benjamin Bennett]

Is there any setting to put rabbitmq into debug logging state?

On Sun, Nov 13, 2011 at 2:50 PM, Benjamin Bennett <benbennett at gmail.com> wrote:
> Here is the stacktrace from the running test cases. I just ran the
> test cases 4 times without a hang on the same vm , then last 3 times
> it hangs.
>
> The tests hang for 20 minutes then the junit run kills the jvm for
> timeout exception.
>
> In the rabbitmq log it is just says the connection abruptly close at
> the same time of the junit runner killed the unit tests.
>
> I was going to attempt to put a timeout on the connection close method
> but that really would be a hack.
>
>
> The stacktrace is exactly the same as this one
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-August/014789.html
> .
> http://pastebin.com/u1Z0Qyrr
>
> Also before the test cases are run I reinstall rabbitmq , delete all
> vhosts and recreate them . So there should not be any memory issues .
>
> The only thread that is in the RUNNABLE state is at the beginning of
> the the stacktrace. I realize this is causing the hang but I don't
> understand why no reply is getting through from rabbit.
>
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
>
> Searching the interwebs points to the remote server not responding.
> http://javaeesupportpatterns.blogspot.com/2011/04/javanetsocketinputstreamsocketread0.html
>
> I can hook up wireshark next to try to diagnose the problem , but I
> thought tracer class would be sufficient.
>
>
>
> On Fri, Nov 11, 2011 at 7:05 AM, Steve Powell <steve at rabbitmq.com> wrote:
>> Hi Benjamin,
>>
>> After investigation of our code, I'm now no longer convinced that
>> your hangs occur because we haven't trapped the EOFException
>> correctly.  We ought to be handling it properly.
>>
>> I cannot reproduce this problem here, yet.
>>
>> Could you please do some more investigation for us?  What would
>> be helpful is for you to take a java stack dump (use jstack) when
>> the hang occurs.
>>
>>    jstack -l <pid>
>>
>> ought to be sufficient, with <pid> the process number of the client JVM.
>>
>> That will help us to find out what is hung where.
>> (It would be most helpful if you could do this on the
>> latest release -- RabbitMQ 2.7.0, but an older one is fine.)
>>
>> Steve Powell
>> steve at rabbitmq.com
>> [wrk: +44-2380-111-528] [mob: +44-7815-838-558]
>>
>> On 3 Nov 2011, at 21:40, Benjamin Bennett wrote:
>>> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-November/015980.html
>>
>