It is fairly obvious that Curt's veto was sustained by all voters except
for me. I'll comment on the vote after I sort out more urgent tasks, such
as tax return and other really interesting administravia.
At 07:14 PM 2/28/2005, Ceki Gülcü wrote:
Curt, your -1 vote is duly registered as blocking
I have found and proved that Log4J does have a deadlock situation in
it's appender failover logic.
In a nutshell heres whats happening. The entire instance of the logger
is syncronized. (Actually the syncronized object is the Category object
from which the Logger is derived.) A caller makes a
How can there be deadlock since the fail over operation will be done on the
same thread? (A given thread is allowed to reacquire the locks which are
already in its possession.)
At 08:10 PM 3/4/2005, Harper, Allen (AHARPER) wrote:
That's ok Ceki. I'm on critical path on a design on a huge
I'm fairly sure I'm correct on this, but if you read the scenario in my note
below your re-entering the logger which is derived from Category which you have
tagged as a syncronized object. So your blocking on the monitor.
JProfiler clearly shows this.
Al
-Original Message-
From: Ceki
Are you running Jprofiler with multiple threads or is it a single threaded
test?
At 08:19 PM 3/4/2005, Harper, Allen (AHARPER) wrote:
I'm fairly sure I'm correct on this, but if you read the scenario in my
note below your re-entering the logger which is derived from Category
which you have
On Fri, 2005-03-04 at 11:28, Harper, Allen (AHARPER) wrote:
We are heavily multi threaded.
The same thing can happen when log4j is rendering the the log message
and you perform a log event.
Refer to bug 24159, I imagine this is somewhat the same flavor of
deadlock.
I'm working on a concurrent
Bingo! I believe it's no different that 2 independent thread calling
into the logger.
Al
-Original Message-
From: Elias Ross [mailto:[EMAIL PROTECTED]
Sent: Friday, March 04, 2005 1:40 PM
To: Log4J Developers List
Subject: RE: Appender, ErrorHanlder fail over deadlock
On Fri,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33855.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
12 matches
Mail list logo
