Discussion:
[jruby-dev] GBR Thead Deadlock Help
(too old to reply)
Ariel Valentin
2013-10-05 17:18:03 UTC
Permalink
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: <Somewhere in our source code>"

"RubyThread-3685559: <Somewhere in our source code>: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 Valentin
e-mail: ariel-5gRS9DP4jy4EIy+m26BRWAC/***@public.gmane.org
website: http://blog.arielvalentin.com
skype: ariel.s.valentin
twitter: arielvalentin
linkedin: http://www.linkedin.com/profile/view?id=8996534
---------------------------------------
*simplicity *communication
*feedback *courage *respect

Loading...