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=20263>. 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=20263 Tomcat 5.0.2 service does not survive logoff [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-05-27 18:57 ------- The problem is with detached java.exe or javaw.exe. The solution is to add the '-Xrs' (to startp JVM options. Reducing signals doesnt installs java.exe's own console control handler, reather inherits one from parent process (procrun). Do not use tomcatw for //ES from 5.0.2, cause it is broken. Use the current binaries from CVS. Here is the explanation from MSDEV. For example, if you install a SIGBREAK handler via the C run-time function signal(), the function installs a handler which overrides the default handler. This causes the application to exit when receiving a CTRL_LOGOFF event even though it was launched from a service. The only solution for java.exe to survive the CTRL_LOGOFF signal is to use the mentioned '-Xrs' option. The Java Docs says: There are two consequences of specifying -Xrs: SIGQUIT thread dumps are not available. User code is responsible for causing shutdown hooks to run, for example by calling System.exit() when the JVM is to be terminated. Remmy does that bother us? If not consider adding '#-Xrs#' to --JavaOptions during install. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
