Chuck answered a similar query recently:
http://marc.info/?l=tomcat-user&m=118113828210257&w=2
Your servlets are serving long-running requests (or are in infinite
loops, dead-locked etc) when you are trying to shutdown tomcat.
The first thing I'd do in this situation is SIGQUIT tomcat to get a
stackdump of the running threads.
With that you can usually determine the changes you need to do to your
servlets, if required.
If the stackdump isn't a help I'd attach a profiler to see where your
servlets are spending the time. I like the one bundled with netbeans.
I'm sure others on the list have their own favourites.
Jon
Peter wrote:
hi all;
when i shutdown tomcat, i found following message in the catalina.out;
2007-6-12 18:18:44 org.apache.catalina.core.StandardWrapper unload
* Waiting for 6 instance(s) to be deallocated*
2007-6-12 18:18:45 org.apache.catalina.core.StandardWrapper unload
*Waiting for 6 instance(s) to be deallocated
*2007-6-12 18:18:46 org.apache.catalina.core.StandardWrapper unload
*Waiting for 6 instance(s) to be deallocated
*2007-6-12 18:18:46 org.apache.catalina.core.StandardWrapper unload
*Waiting for 333 instance(s) to be deallocated*
2007-6-12 18:18:47 org.apache.catalina.core.StandardWrapper unload
*Waiting for 333 instance(s) to be deallocated*
2007-6-12 18:18:48 org.apache.catalina.core.StandardWrapper unload
* Waiting for 333 instance(s) to be deallocated*
anyone has a idea about the about messages, does it means that there
is dead
lock in the program?
or some connection are not closed?
thank you for ideas!
peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
