>Hello all, > >I am running tomcat 4.0.3 (on windows and linux) and using the com.oreilly.servlets class DaemonHttpServlet to provide socket based connections to legacy >clients. I basically built right off the example in the O'Reilly servlets book and everything works fine. Fine, that is, until I try to shut down Tomcat. The threads >attached to the Daemon servlet just don't go away. However if I hit them with the legacy client (causing it to get a connection exception on the socket) the >servlet shuts down, although with some really nasty error messages in the tomcat log. > >Has anyone else seen this behavior? Is there some simple "gotcha" that I missed? In my destroy() method I am calling super.destroy() and it is the very first >thing I call in that method. Is there something else I should be doing or checking so that it shuts down cleanly? I can post more details, including code >samples and log output if anyone thinks it will help. > >Thanks, > >Chuck
>Samar Uppal wrote: >>it is not possible for threads to keep running when the server has been shut down. >>they must be starting again when you restart the server That's just it, tomcat never shuts down, it just hangs until I hit the servlet with the client, which causes an explosion of exceptions in the tomcat log and then all of the tomcat java processes die off. Also, since I left it out in the above, I am using Java 1.4 for this. Chuck ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
