Took me a while to notice that the quoted post is over a year old. I didn't see any follow up in the archives. In the original posting, that it is a block between a lock on a PrintStream and a RootLogger suggest to me that System.out might have been redirected to log4j and when log4j attempted to write to LogLog, it blocked. But that is just a guess, however anything that redirects System.out or .err to log4j would be likely to encounter deadlocks.

On Sep 21, 2007, at 10:18 AM, James A. N. Stauffer wrote:

After years of using log4j I also encountered this.  Is it a freak,
rare occurance or is there a cause that can be addressed?

Found one Java-level deadlock:
=============================
"ConnectorThread jdbc:weblogic:mssqlserver4:[EMAIL PROTECTED]:1433":
  waiting to lock monitor 0x000e00d8 (object 0xa63067d0, a
org.apache.log4j.spi.RootCategory),
  which is held by "main"
"main":
  waiting to lock monitor 0x000e0120 (object 0xa6305750, a
sps.webec.sql.ConnectionBroker),
  which is held by "ConnectorThread
jdbc:weblogic:mssqlserver4:[EMAIL PROTECTED]:1433"


On 5/25/06, Iyer, Vidya <[EMAIL PROTECTED]> wrote:
Hi,

I'm running an application with several threads, and at the end of the program, each thread logs an info statement that it is shutting down. Unfortunately, I periodically see two threads get deadlocked with the below error. The docs say that log4j is supposed to be thread safe, but it looks like there might be a bug in the synchronized code. Has anyone experienced this before?

Found one Java-level deadlock:
=============================
"MessageReader-15":
waiting to lock monitor 0x0809f394 (object 0x666b4788, a java.io.PrintStream),
  which is held by "main"
"main":
waiting to lock monitor 0x0809f494 (object 0x65e061a0, a org.apache.log4j.spi.RootLogger),
  which is held by "MessageReader-15"


Thanks,
Vidya




--
James A. N. Stauffer        http://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to