Refer to this:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24159
If any of your objects look like this, and if you log it from one thread, and call set in another, you can deadlock. I suggest you don't do any sort of logging while holding any locks. (Remove the log in the set method...)
class State { Logger log1;
synchronized void setState() { // Something takes a long time here log.debug("hello world"); }
synchronized Object getState() { }
public String toString() { return "state=" + getState(); } }
The above scenario is quite special. It is yet unclear if the deadlock observed by Prithi is related.
-- Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
