On Fri, Jul 27, 2012 at 12:02 PM, Kyle R. Burton 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 Ke
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 keywor
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 wrote:
> I encountered a deadlock on one of our production systems (one out
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
