Re: Problems with DaemonHttpServlet not shutting down

Did you get an answer? If not, what OS are you using? Also, you should
clean up any network or database resources before calling destroy, that
may help.

Mike

On Fri, 2003-01-10 at 09:20, Chuck Hirstius wrote:

    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