Agreed,
and if you have any session information and the session can't be (for
whatever reason) be de/serialized, it would indeed be a very bad idea to
restart tomcat.
Christoph
Robert Harper wrote:
The best practice is to find the leak and fix it. Restarting is a cover up
to a problem that
The best practice is to find the leak and fix it. Restarting is a cover up
to a problem that may cause bigger problems down the road as the project
scope increases. You can do this but it only hides the real problem and if
someone replicates you site and forgets to write or enable the script, then
