Try running the "stop" command several times.
If you eventually get a bunch of socket exceptions on the screen,
you know that it worked (the errors appear if you run stop, and there
is no tomcat instance to stop).
I think there are some problems with some JVMs, which are not
stopping all threads properly. I get this behaviour on HP-UX, and
used to get it on Solaris until I upgraded to the latest JVM.
> -----Original Message-----
> From: Blair Tingey [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, December 15, 2000 7:31 PM
> To: [EMAIL PROTECTED]
> Subject: Can't stop tomcat
>
> Hello,
>
> I have installed Tomcat 3.2 on Solaris and I have not modified any of the
> XML files so this is a pretty generic install. After starting tomcat using
> ./tomcat.sh start
>
> I issue the command: ./tomcat.sh stop to stop Tomcat and the process
> does not stop.
>
> It looks as if classes are unloaded and I get a Tomcat Stopped message,
> but if I look at the processes I still have the Tomcat process running.
>
> What can I do to stop Tomcat by using ./tomcat.sh stop ?
>
> Thanks,
> Blair Tingey
