On 27/02/12 2:12 PM, Christopher Schultz wrote:
It would be nice if it showed as "disabled" (to use the mod_jk
terminology for an instance which is running but gets no new
sessions).
It's just a coincidence that no new sessions are being created --
because sessionless requests /should/ be sent to the new version. The
old version simply isn't used any more... it's not actually in any
different state than the new version.
Now this is interesting. What happens if our application defines a static class
or other resource? Would both the new and old code be simultaneously loaded in
the same JVM at the same time? Is there some way we might have been able to
create an object in memory which is causing the requests to be handled by the
wrong application? We are doing a few tricky things with parsing incoming
requests which isn't a standard Tapestry way of working.
Tomcat doesn't show any memory leaks when we press that button in the Tomcat
Manager, but perhaps there is something in our code which confuses the code
from the old and new applications? Is that even possible?
The feature request for the auto-shutdown issue is here:
https://issues.apache.org/bugzilla/show_bug.cgi?id=52777 I took the liberty of
taking your notes in this list into the task so that the ideas are not lost.
Cheers
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
