Re: Occasional NoClassDefFoundError, but disappears after couple of restarts

["A. Rothman" <am...@amichais.net>]

I've opened https://issues.apache.org/bugzilla/show_bug.cgi?id=48097 
with a sample jsp that recreates the error.

Mark Thomas wrote:

> A. Rothman wrote:
>   
>> A couple months ago I had a slightly different setting but with the same
>> strange result - NoClassDefFoundErrors which occurred on a particular
>> jsp page in my app, but only if it was the first jsp accessed following
>> a restart (and remained in the error state until the next restart). If
>> it was not the first jsp accessed, then everything came up fine (with
>> nothing in the configuration or app changing in between). I also figured
>> it's some classloader bug in Tomcat, not entirely a race condition
>> (since it did happen consistently), but something that manifests itself
>> depending on the order of class loading.
>>     
>
> If you can provide a cut-down copy of that JSP that reproduces the
> problem on a clean Tomcat install, I'd be happy to take a look. Just
> create a new bugzilla entry and provide the JSP as an attachment.
>
> Mark
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>   

Re: Occasional NoClassDefFoundError, but disappears after couple of restarts

["A. Rothman" <am...@amichais.net>]

To anyone who may stumble upon this thread looking for solutions - this 
bug has been investigated and fixed by Konstantin Kolinko 
(https://issues.apache.org/bugzilla/show_bug.cgi?id=48097). The fix 
should be available in Tomcat 6.0.21 and later. 
<ma...@gmail.com>

A. Rothman wrote:

> I've opened https://issues.apache.org/bugzilla/show_bug.cgi?id=48097 
> with a sample jsp that recreates the error.
>
> Mark Thomas wrote:
>
>> A. Rothman wrote:
>>  
>>> A couple months ago I had a slightly different setting but with the 
>>> same
>>> strange result - NoClassDefFoundErrors which occurred on a particular
>>> jsp page in my app, but only if it was the first jsp accessed following
>>> a restart (and remained in the error state until the next restart). If
>>> it was not the first jsp accessed, then everything came up fine (with
>>> nothing in the configuration or app changing in between). I also 
>>> figured
>>> it's some classloader bug in Tomcat, not entirely a race condition
>>> (since it did happen consistently), but something that manifests itself
>>> depending on the order of class loading.
>>>     
>>
>> If you can provide a cut-down copy of that JSP that reproduces the
>> problem on a clean Tomcat install, I'd be happy to take a look. Just
>> create a new bugzilla entry and provide the JSP as an attachment.
>>
>> Mark
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>   
>