That might be the simpliest but using kill to stop tomcat can prevent services
from properly shutting down potentially causing data loss depending on your
application. In a development environment that is likely a good solution but
in a production environment I don't think that is a good idea.
Changing the shutdown name seems like the best solution for my uses. That is
effectively the password mechanism I was hoping the Bootstrap class supported.
I might also look into how the jvsc would work but I still think the tomcat
shutdown script is going to be the safest method.
Thanks for the response,
Fu-Tung
--- On Thu, 8/21/08, Mark Thomas <[EMAIL PROTECTED]> wrote:
> From: Mark Thomas <[EMAIL PROTECTED]>
> Subject: Re: tomcat instances on different ports running as different users
> can anyone shutdown?
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Date: Thursday, August 21, 2008, 10:12 PM
> The simple solution (from Filip):
>
> Set the shutdown port to -1.
>
> Use kill to stop Tomcat.
>
> Mark
>
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
