https://bz.apache.org/bugzilla/show_bug.cgi?id=65970
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Christopher Schultz <ch...@christopherschultz.net> ---
This situation was probably caused by a very unusual circumstance, such as a
power failure or kill-9 signal.
It's not clear what you are asking for, here. If CATALINA_PID exists and there
is an existing process matching that PID, then Tomcat will not start because it
looks like Tomcat is already running.
With a low PID like that, it's probably a process that runs on startup, and,
with a stale PID file it's very likely to match another process that was
started on startup as well.
A better solution for you might be to place your PID file on volatile storage,
or somewhere the OS will clear-out upon reboot, like /tmp. Not all OSs
clear-out /tmp on reboot, but some of them do. Another option would be to
instruct your init system to delete certain files (including the Tomcat PID
file) early-on in the boot process to make sure the PID file just doesn't exist
at all.
--
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
