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 40947] - Stopping the server should not rely on passing a string to a port on localhost.
Date Thu, 07 Dec 2006 22:13:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40947>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40947





------- Additional Comments From shankarunni@netscape.net  2006-12-07 14:13 -------
(In reply to comment #2)
> On Unix, this is already possible using the 'jsvc'-Binary.
> AFAIK simply remove the 'shutdown'-element from server.xml

"jsvc" doesn't do any magic - it just kills the process. You'd prefer to kill
tomcat cleanly (by making it shut down cleanly somehow) - which is why you have
this mechanism to tell it to do so. 

Of course, on non-Windows boxes, Tomcat catches TERM signals and exits cleanly.

And AFAIK, setting the Server's port to "-1" disables the opening of the port,
and then you have to be logged in as the user that Tomcat is running under (or
as root) in order to kill it (by sending it a "TERM" signal).

So that should take care of many of the security concerns on Unix.

On Windows, I'm not sure what signals terminate Tomcat if it's running as a
service - if it's running as a command-line process, then CTRL-BREAK should do it.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message