Full stack traces for those three threads would help. Look through the stacks for any code that might be yours and see what it is you are doing with logging in that code.
Note that the situation you have indicated might not be an issue - logging tends to be single-threaded (otherwise the log file would be garbage). There is some other thread that has 'monitor' locked and probably released it a microsecond after you took the stack trace. It is usually better to take two or three stack traces, about 10 to 20 seconds apart, and compare them looking for code that might be looping (the thread stack remains the same for each dump, and the thread is not waiting on an http socket). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197743#4197743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197743 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
