Hi,
I'd like to bump this issue once more.
I finally had some time to run some more experiments to see what
happens with TagHandlers that implement JspIdConsumer. My setup is
Tomcat 6 + MyFaces + JSF CarDemo, and I'm using AspectJ to trace
creation and garbage collection of objects implementing JspIdConsumer.
My experiments indicate the following:
1. JspIdConsumer instances do NOT get garbage collected after a page
has finished processing.
2. JspIdConsumer instances do NOT get garbage collected after a
session times out.
3. SOME JspIdConsumer instances DO get garbage collected when a given
JSP-generated page is reloaded or accessed in a different session.
To obtain these results I ran Tomcat with very little heap memory (it
seems it starts fine with the 64M default), loaded the car demo in
several browser sessions and ran through all the other JSP/Servlet
examples that come with Tomcat to increase the memory consumption and
trigger GC. Unfortunately I don't have the time and tools to do a
proper stress test.
In any case, considering the specification of JspIdConsumer, which
states that instances may never be reused, the caching of these
instances as it is done in current JSPs is unnecessary, and since
these instances don't seem to be GC'd, this seems to be a memory leak.
Could the developers confirm this or suggest what is going on that I'm
missing?
Jochen Wuttke
-----------
PhD Candidate
Faculty of Informatics
University of Lugano
Via Giuseppe Buffi 13
CH-6904 Lugano - Switzerland
phone: +41 58 666 4308
www.inf.unisi.ch/phd/wuttke
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]