logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Krishna <suresh.madhuva...@oracle.com>
Subject Re: log4j does not log when the application crashes for some reason
Date Mon, 29 Jun 2009 20:49:10 GMT
Hi Ceki,

The problem is that it is the application that crashes but _not_ due to 
log4j. We have lot of info/warn/error statements in probably each and 
every class. But when the appplication crashes for some reason, the log 
file does not have the recent stack trace before the application died, 
but it just has a message that an error occurred and could not log.

On the condole the following message appears :
*** This message goes through <appName> to LOG4J
*** This message bypasses the <appName> / LOG4J ***
But in the log file, i see only the first message but not the second one.

Any ideas ?


Ceki Gulcu wrote:
> Hello Krishna,
> If your application runs out of memory at an arbitrary point in code,
> log4j will not be invoked, and cannot log. However, you also seem to
> imply that log4j is somehow responsible for the runtime exception. In
> that case, could you please be more specific?
> Suresh Krishna wrote:
>> Hi,
>> We are using the the log4j for our applications. Recently we have 
>> come to a blocking point that, the log4j does not log the exceptions 
>> or what happened to the log file. Our application may crash with the 
>> *out of memory error* or some *runtime exception*. In both the cases 
>> the log4j does not log the exception.... is there any way to deal 
>> with this ?
>> Appreciate any response on this.
>> Thanks,
>> Krishna

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message