https://bz.apache.org/bugzilla/show_bug.cgi?id=57801
Rainer Jung <rainer.j...@kippdata.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Hardware|PC |All
--- Comment #1 from Rainer Jung <rainer.j...@kippdata.de> ---
Either you should integrate your Tomcat stop (and probably start) into your
system shutdown/startup (rc scripts or whatever methodology your system uses)
or you rely on doing it by hand.
In the latter case, Tomcat does not get any info about the system shutdown and
can not react on it. Trying to find out whether the found process after reboot
actually is a Tomcat process or something else is not the task of the start
script.Integrating it will be error prone and hard to maintain cross platform.
If you start by hand and get the cited error, you need to check the other
process (like you did) and if it is something else and Tomcat is not running,
purge the old PID file.
We could probably make the message
"Existing PID file found during start.
Tomcat appears to still be running with PID 3387. Start aborted."
a bit better
"Existing PID file found during start.
Tomcat appears to still be running with PID 3387. Start aborted.
If the process with PID 3387 is not a Tomcat process, remove the PID file
NAME_OF_PID_FILE_HERE and try again."
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
