logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Randall <javabr...@gmail.com>
Subject Re: bizarre NPE exception
Date Tue, 17 Nov 2009 00:08:30 GMT
JK> Given that it happens after a redeploy cycles, it is likely the infamous
Tomcat bug (though they probably don't consider it one) where normally
static final constants are nulled by Tomcat code to work around garbage
collection bugs while leaving the classloader in-tact

+1

On Tue, Nov 17, 2009 at 10:37 AM, Jacob Kjome <hoju@visi.com> wrote:

>
> Is this actually bombing out your code or is the exception just printed to
> System.err?  If the latter, then this does not constitute and "uncaught
> exception... requiring immediate attention".
>
> Given that it happens after a redeploy cycles, it is likely the infamous
> Tomcat bug (though they probably don't consider it one) where normally
> static final constants are nulled by Tomcat code to work around garbage
> collection bugs while leaving the classloader in-tact.  Therefore, next time
> the constant, which in normal usage cannot possibly be null, is reference
> and a method on it is executed, a NullPointerException results.
>
> You say you are not using Tomcat, but your server might be using Tomcat
> under the covers.  In any case, please indicate whether the exception
> actually interrupts your program or the stack trace is simply printed to
> System.err.  Though, if Tomcat's classloader manipulation is the culprit,
> there's not much we can do in either case.
>
>
> Jake
>
>
> On 11/16/2009 2:03 PM, Pat Farrell wrote:
>
>> Curt Arnold wrote:
>>
>>> The log4j 1.2 date and date caching code is problematic and was replaced
>>> in the abandoned log4j 1.3 effort...
>>>
>>
>>  From the log4j FAQ, it says:
>>>
>>
>> "If for any reason, log4j throws an uncaught exception, please send an
>> email to the log4j-user@logging.apache.org  mailing list. Uncaught
>> exceptions are handled as serious bugs requiring immediate attention. "
>>
>> I think I'm seeing an uncaught exception. If there is really going to be
>> "immediate attention" what do I do to help?
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message