![]() ![]() ![]() These are listed roughly in the order I would try them, depending on the evidence collected: waiting to lock (a 11.Http11Protocol$Http11ConnectionHandler)Īt 11.Http11Protocol$Http11ConnectionHandler.createProcessor(Http11Protocol.java:630) : BLOCKED (on object monitor)Īt (Unknown Source)Īt (DelegatingConstructorAccessorImpl.java:27)Īt .newInstance(Constructor.java:513)Īt 0(Class.java:355)Īt (Class.java:308)Īt .createBeanClassInstance(Container.java:630) What would cause a JVM to block, .newInstance? Obviously some resource "is scarce" but which resource? In this case, I see all sorts of classes/methods blocked, including jvm internal classes, jboss classes, log4j, etc, in addition to application classes (including jdbc and lucene calls) some database record lock or file system lock problem which caused other threads to wait.Ģ) All blocked threads would block on the same class/method (e.g. ![]() In the past blocked thread usually had this issue:ġ) some obvious bottleneck: e.g. We got a stack trace before the application restart and I found some surprising results: of 527 threads, 463 had thread state BLOCKED. We had a recent situation where the application appeared -to the end user-to hang. The log had no errors/exceptions/evidence of problems-probably because the JVM was killed before it could generate an error message. I believe they shut down the site before the heap dump finished. Our operations team saw that the site wasn't responding, took a stack trace, then shut down the instance. A 3.8 Gb Hprof file indicated that the JVM was dumping-its-heap when this "blocking" occurred. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |