You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/12/01 09:41:18 UTC
DO NOT REPLY [Bug 41214] Deadlock with RollingFileAppender
https://issues.apache.org/bugzilla/show_bug.cgi?id=41214
Deepak <bd...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bdeepak.x@gmail.com
--- Comment #25 from Deepak <bd...@gmail.com> 2008-12-01 00:41:17 PST ---
The problem is pretty consistent and seems to be happening on high traffic
servers. Here is one that I caught on my weblogic server. This lock will
eventually bring the server down since the request processor / servlet engines
will be unable to process any further requests.
I am not sure about the lock scalability thing. My logs indicate a positive
deadlock condition. Is this going to be fixed anytime soon ?
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
BEA JRockit(R) (build
R26.4.0-63_CR302700-72606-1.5.0_06-20061127-1108-win-ia32, )
OS - Windows 2000 SP4
Log4j version - 1.2.15
Server - Weblogic 10 SP1
Deadlocks encountered on a web application built on Struts 1.1
Circular (deadlocked) lock chains
=================================
Chain 2:
=================================
"[STUCK] ExecuteThread: '39' for queue: 'weblogic.kernel.Default
(self-tuning)'" id=11799 idx=0xee tid=6520 waiting for
org/apache/log4j/Logger@0x05AE0EF0 held by:
"[STUCK] ExecuteThread: '28' for queue: 'weblogic.kernel.Default
(self-tuning)'" id=6044 idx=0x9c tid=6496 waiting for
org/apache/log4j/RollingFileAppender@0x0B1E4CB8 held by:
"[STUCK] ExecuteThread: '39' for queue: 'weblogic.kernel.Default
(self-tuning)'" id=11799 idx=0xee tid=6520
=================================
Thread 39
=================================
"[STUCK] ExecuteThread: '39' for queue: 'weblogic.kernel.Default
(self-tuning)'" id=11799 idx=0xee tid=6520 prio=1 alive, in native, blocked,
daemon
-- Blocked trying to get lock:
org/apache/log4j/Logger@0x05AE0EF0[thin lock]
at jrockit/vm/Threads.sleep(I)V(Native Method)
at
jrockit/vm/Locks.waitForThinRelease(Ljava/lang/Object;I)I(Unknown Source)
at
jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown
Source)
at
jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown
Source)
at
org/apache/log4j/Category.callAppenders(Lorg/apache/log4j/spi/LoggingEvent;)V(Category.java:201)
at
org/apache/log4j/Category.forcedLog(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V(Category.java:388)
at
org/apache/log4j/Category.debug(Ljava/lang/Object;)V(Category.java:257)
=================================
Thread 28
=================================
"[STUCK] ExecuteThread: '28' for queue: 'weblogic.kernel.Default
(self-tuning)'" id=6044 idx=0x9c tid=6496 prio=1 alive, in native, blocked,
daemon
-- Blocked trying to get lock:
org/apache/log4j/RollingFileAppender@0x0B1E4CB8[thin lock]
at jrockit/vm/Threads.sleep(I)V(Native Method)
at
jrockit/vm/Locks.waitForThinRelease(Ljava/lang/Object;I)I(Unknown Source)
at
jrockit/vm/Locks.monitorEnterSecondStage(Ljava/lang/Object;I)Ljava/lang/Object;(Unknown
Source)
at
jrockit/vm/Locks.monitorEnter(Ljava/lang/Object;)Ljava/lang/Object;(Unknown
Source)
at
org/apache/log4j/AppenderSkeleton.doAppend(Lorg/apache/log4j/spi/LoggingEvent;)V(AppenderSkeleton.java:210)
at
org/apache/log4j/helpers/AppenderAttachableImpl.appendLoopOnAppenders(Lorg/apache/log4j/spi/LoggingEvent;)I(AppenderAttachableImpl.java:65)
at
org/apache/log4j/Category.callAppenders(Lorg/apache/log4j/spi/LoggingEvent;)V(Category.java:203)
^-- Holding lock: org/apache/log4j/Logger@0x05AE0EF0[thin lock]
at
org/apache/log4j/Category.forcedLog(Ljava/lang/String;Lorg/apache/log4j/Priority;Ljava/lang/Object;Ljava/lang/Throwable;)V(Category.java:388)
at
org/apache/log4j/Category.debug(Ljava/lang/Object;)V(Category.java:257)
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org