DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33711>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33711





------- Additional Comments From [EMAIL PROTECTED]  2005-04-06 17:58 -------
(In reply to comment #18)
> What did you test exactly (CVS version ?) ? Still using log4j for 
everything ?
> Do you have any idea on where the reference to the classloader would be 
kept ?

I updated to CVS head just after you committed the changes (31/3 maybe? can't 
remember).

The content of my test WAR is:
>jar -ft leak.war
index.jsp
META-INF/context.xml
META-INF/MANIFEST.MF
META-INF/
WEB-INF/classes/
WEB-INF/classes/BigServlet.class
WEB-INF/lib/
WEB-INF/lib/commons-logging.1.0.3.jar
WEB-INF/lib/log4j.1.2.8.jar
WEB-INF/web.xml
WEB-INF/


Context.xml is simply:
<Context antiResourceLocking="true" antiJARLocking="true" >
</Context>


BigServlet simply has a static byte[] to allocate 20MB, initialised in the init
() method, and also logs a message.
Web.xml simply specifies it is loaded on startup, and that everything in the 
web app required the user to be in a given role.  The JSP simply displays the 
remoteUser and SessionID.

[Note: this configuration above is just for my test web app and we try to work 
around it.  For production we include the Log4J jar only in our web app, and 
then use separate jdk logging for anything that is done through commons-
logging.]

As for ideas as to what is holding the reference, no I don't have ideas.  The 
profiler I'm currently evaluating isn't helping me there :-(  The best I used 
so far (and was using back when I first reported) was YourKit4.0, but my eval 
has expired.

K.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to