A couple of questions: How are you deploying the web app? Is the
daemon thread aware of the Servlet lifecycle?
I have observed that when deploying via the Tomcat manager, there are
cases where the web app is stopped and restarted erroneously.
Basically, it starts after a deploy, then within a
I believe I'm seeing a memory leak as a result of a Manager
deploy/undeploy. I have a very simple test case: a Servlet that has a
static field that refers to an object (Foo) that allocates a large chunk
of memory. I've instrumented both the Servlet (init(), destroy(), and
finalize()) and Foo
Try running the Tomcat VM with the -Djava.awt.headless=true system
property (set it in an environment variable named CATALINA_OPTS).
On Tue, 2003-03-18 at 16:31, Georges Roux wrote:
Hello everybody,
Hi run Tomcat 4.1.18 Standalone on Linux debian(sid)and use J2sdk1.4.1_01.
I have a servlet
I'm seeing a potential bug in Tomcat (tested in both 4.1.12
and 4.1.21 Beta) and wanted a sanity check...
Here's the scenario:
I am deploying a simple webapp via the Tomcat 4.1.X manager.
After deploying the webapp once, I update the timestamp on
/WEB-INF/web.xml and redeploy (undeploy followed
