I don't see any problem with adding an option to LoaderInterceptor11 to
force it to use a SimpleClassLoader (the descendent of AdaptiveClassLoader)
even on a Java2 platform.  There are some trade-offs, since
SimpleClassLoader is really meant for Java1.1 platforms, but for a lot of
people they don't look too serious.

This is a little bigger decision than I want to make on my own, so I've
included the Developer List in the reply in case one of the other developers
has comments/suggestions.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 05, 2002 6:47 PM
Subject: Possible Explanation - Re: DO NOT REPLY [Bug 5684] - WEB-INF/lib
jar file loading and operations problems.


> Hi Bill,
>
> I downloaded the 3.3 source code and did some sniffing.  From what I can
> tell, here is why 3.2 works and 3.3 does not work with regards to jar
files
> and it's classes.
>
> TC 3.2 - LoaderInterceptor uses new instances of the AdaptiveClassLoader
> (and subclasses for jdk12 support) to handle a context init.  This
> classloader overrides classloader methods and does everything correctly.
> That's why it has no problem with loading classes from jar files using zip
> methods or jar file locking.  It closes it's jar files after reading it's
> class files.
>
> TC 3.3 - LoaderInterceptor11 uses new instances of the jdk's
URLClassloader.
> What more can I say.  Tomcat has no control over URLClassloader and it's
> operations.  The problems you and Bojan pointed out are out of Tomcat's
> control.
>
> I'd like to know what you think.  If I'm correct, the question is whether
or
> not you folks are going to punt to Sun.  This will let me know what my
> course of action will be.
>
> Regards,
> Mike
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, January 05, 2002 12:34 PM
> Subject: Re: DO NOT REPLY [Bug 5684] - WEB-INF/lib jar file loading and
> operations problems.
>
>
> Bill,
> Is this patch in the 1/4 nightly build of 3.3?  Which .java file was it?
>
> Regards,
> Mike
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, January 04, 2002 4:50 PM
> Subject: DO NOT REPLY [Bug 5684] - WEB-INF/lib jar file loading and
> operations problems.
>
>
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5684>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> INSERTED IN THE BUG DATABASE.
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5684
>
> WEB-INF/lib jar file loading and operations problems.
>
>
>
>
>
> ------- Additional Comments From [EMAIL PROTECTED]  2002-01-04
> 18:50 -------
> There was a missing close statement in the app-ClassLoader.  I've added it
> in,
> so that the jar file shouldn't stay open.  This may fix part 1 (since 3.3
> typically does GC much less often then 3.2).
>
> It is possible (if very unlikely) that being able to delete the jar file
may
> help with 2.
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to