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