Sure, i think thats the final goal. For us its like a dead lock.
We want to know what went wrong with the application and we have all the
logging possible to know in the code. But at the time of crash, we dont
get any log4j logging. So, we dont yet know what causes this crash and
we want to see
> -Original Message-
> From: Suresh Krishna [mailto:suresh.madhuva...@oracle.com]
> Subject: log4j does not log when the application crashes for some reason
> 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
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,
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,
