tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 4536] New: - Tomcat doesnt kill threads while shutdown
Date Wed, 31 Oct 2001 09:05:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4536>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4536

Tomcat doesnt kill threads while shutdown

           Summary: Tomcat doesnt kill threads while shutdown
           Product: Tomcat 3
           Version: 3.2 Final
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: v_ignatius@yahoo.com
                CC: v_ignatius@yahoo.com


Hi,
  Am using tomcat 3.2.2 and am running in to problems when i bootstrap a sevlet 
which creates couple of thread in the same VM as tomcat.
  The exact problem is this.I have a servlet which creates a couple of threads 
which will be alive until the VM exits.The thread creation is done in the init 
method if the servlet.I've bootstrapped the servlet and am starting the 
server.The init method is called and the threads are being created and the 
server is started at the default port.Now when i start the server again without 
shutting down the server it calls the init method of the servlet creates the 
thread in a new VM and eventually when it tries to bind the server to the 
default port it throws a BindException(Obviously b'cos the server is already 
running in the default port)but does not the kill the VM ie it does not call 
the System.exit and hence the a new java process is created and this can only 
be killed using kill command.If i attempt to start the server without shutting 
the server n times ,n times it throws bind exception and it created n java 
processes.I even decomplied the tomcat source and found that when a bind 
exception occurs System.exit is not called.Tomcat first loads the bootstrapped 
servlets and then only binds the service.Is there any fix or workaround for 
this.

Regards,
Vijay

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message