On Thu, 2003-12-18 at 15:50, Milind Rao wrote:
> I have patched org.apache.log4j.varia.FallbackErrorHandler to add a
> getBackupAppender() method. I patched it against
> jakarta-log4j on the :pserver:[EMAIL PROTECTED]:/home/cvspublic CVS server. If this
> is not the right CVS Server to
> be u
psmith 2003/12/17 21:16:57
Modified:src/java/org/apache/log4j/varia FallbackErrorHandler.java
Log:
Applied Patch submitted by Milind Rao to expose the
backupAppender property.
Revision ChangesPath
1.7 +9 -0
jakarta-log4j/src/java/org/apache/log4j/varia/Fall
I have patched org.apache.log4j.varia.FallbackErrorHandler to add a
getBackupAppender() method. I patched it against
jakarta-log4j on the :pserver:[EMAIL PROTECTED]:/home/cvspublic CVS server. If this
is not the right CVS Server to
be used, please let me know.
Regards
Milind
Index:
Thanks Elias. I'll comment the log statements in synchronized methods and try.
Is there any log4j patch for this? I can see some one working on fixing it.
Elias Ross <[EMAIL PROTECTED]> wrote:
On Wed, 2003-12-17 at 13:04, Prithi wrote:> We are seeing a dead lock problem with log4j, during load te
I am using Log4j's MDC in my web applications.
MDC stores context objects using ThreadLocal storage.
http://cvs.apache.org/viewcvs.cgi/jakarta-log4j/src/java/org/apache/log4
j/MDC.java?rev=1.15&view=auto
-Sean
> -Original Message-
> From: Raymond DeCampo [mailto:[EMAIL PROTECTED]
> Sen
On Wed, 2003-12-17 at 13:04, Prithi wrote:
> We are seeing a dead lock problem with log4j, during load test. Has anyone seen this
> before. I have attached a sample log below.
>
> Any help greatly appreciated.
>
> Thanks - Prithi
Refer to this:
http://nagoya.apache.org/bugzilla/show_bug.cgi?
All,
I was recently thinking about adding some NDC logging to my servlet, but
I was concerned (perhaps unnecessarily) by some of the things I read in
the docs and the source code.
Since I am in a servlet container I am not in control of my threads. So
it is difficult to know when to call NDC.
We are seeing a dead lock problem with log4j, during load test. Has anyone seen this before. I have attached a sample log below. Any help greatly appreciated. Thanks - Prithi "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x2f8f88 nid=0x38 waiting on monitor [0xe4481000..0xe4481