Thread Dead Lock

Ruby JRuby
1

I am trying to generate a GBR for an issue that I have run into with a
Thread Deadlock, however it is incredibly difficult to reliably
reproduce.
I have only been able to reproduce it once while I was running load
tests
on our application, which runs over several days.

This is the output from our thread dump:

Found one Java-level deadlock:
=============================“http-/192.168.220.196:8080-8192”:
waiting to lock monitor 0x00007fca797bffa8 (object
0x00000005a6894000, a org.jruby.internal.runtime.ThreadService),
which is held by
"http-/192.168.220.196:8080-598"“http-/192.168.220.196:8080-598”:
waiting to lock monitor 0x00007fca390d0600 (object
0x00000006dd8466c0, a org.jruby.RubyThread),
which is held by “RubyThread-3685559: ”

“RubyThread-3685559: :106”:
waiting to lock monitor 0x00007fca797bffa8 (object
0x00000005a6894000, a org.jruby.internal.runtime.ThreadService),
which is held by “http-/192.168.220.196:8080-598”

Does anyone have any guidance on trying to open good GBRs for thread
deadlock race conditions?

Ariel V.
e-mail: [email protected]
website: http://blog.arielvalentin.com
skype: ariel.s.valentin
twitter: arielvalentin
linkedin: Sign Up | LinkedIn

2

I have seen a similar deadlock that should be fixed in 1.7.5:

In the case where this doesn’t solve your issues, please open a new
issue and we’ll help you investigate.

  • Charlie

On Tue, Oct 15, 2013 at 10:24 AM, Ariel V.

3

Headius,

Thanks for pointing out this possible fix; I am on 1.7.4 right now and
will
not be able to upgrade right away. Once I do I’ll try and run the load
tests on the system and see if this helps mitigate my issue.

Ariel V.
e-mail: [email protected]
website: http://blog.arielvalentin.com
skype: ariel.s.valentin
twitter: arielvalentin
linkedin: Sign Up | LinkedIn

*simplicity *communication
*feedback *courage *respect

On Tue, Oct 22, 2013 at 5:13 PM, Charles Oliver N.