Hi Nealie, >From the thread dump, while there certainly is a lot of recursion going on, it doesn't look to me like the stack is blowing. Rather, many of the threads appear to be WAITING on the reentrant lock used for coordination on the java.util.concurrent.HashMap that stores the interned keywords.
Presumably all of the Jetty worker threads became blocked on this lock, as the web service stopped process HTTP requests altogether. Note, however, that other threads( like the AMQP consumers) continued to work just fine. Thanks, -Paul SC On Fri, Jul 27, 2012 at 12:12 PM, Neale Swinnerton <ne...@isismanor.com>wrote: > The infinite recursion on Keyword.intern() looks very similar to this > bug, fixed in 1.3.0.... > > http://dev.clojure.org/jira/browse/CLJ-444 > > Neale > {t: @sw1nn, w: sw1nn.com } > > > On Fri, Jul 27, 2012 at 5:02 PM, Kyle R. Burton <kyle.bur...@gmail.com> > wrote: > > I encountered a deadlock on one of our production systems (one out of > > 3) last night. Looking at a thread dump of the JVM, there are several > > (over 200) threads that are all waiting on a > > java.util.concurrent.locks.ReentrantLock from Keyword.intern. > > > > I've put up the thread dump and information about the os and jvm > versions here: > > > > https://github.com/relaynetwork/20120727-deadlock-issue > > > > The part of our application that deadlocked is a web service that uses > > Compjure and Jetty. Other parts of the application did not deadlock > > (we have AMQP consumers that were still processing successfully). > > > > I have since restarted the service and it is processing again. I'm > > not sure what to look at next, can anyone suggest a next step for > > determining the cause? > > > > > > Best Regards, > > > > Kyle Burton > > > > -- > > Twitter: @kyleburton > > Blog: http://asymmetrical-view.com/ > > Fun: http://snapclean.me/ > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Clojure" group. > > To post to this group, send email to clojure@googlegroups.com > > Note that posts from new members are moderated - please be patient with > your first post. > > To unsubscribe from this group, send email to > > clojure+unsubscr...@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/clojure?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
