Thanks to Rodney and Rogelio, Examination of a thread dump did indeed show user threads hanging about from the xml-rpc service. Commenting out the xml-rpc service settings in TR.props solved the problem as I wasn't using the service.
Presumably this must be a problem if the xml-rpc service is required for the webapp? Should there be an issue on scarab? Regards, Peter On Tue, 2002-10-15 at 01:21, Rodney Schneider wrote: > On Tue, 15 Oct 2002 06:17, you wrote: > > > Hi all, > > > > When I stop the tdk2.2-b3 version of catalina, log/catalina.out shows it > > stopping. However, the jvm processes still appear in the process list > > and attempting to start catalina again results in a > > java.net.bindException Address already in use :8080. > > If there is a user (non-daemon) thread still running, it will keep the JVM > alive. Try this: > > cd $TDK_HOME/bin > ./catalina.sh run > > Then press <Ctrl>-<\> to get a full JVM thread dump. That will help you > analyse which threads are running in that JVM. I think you can also do this > by sending a SIGQUIT signal to the JVM process if you use the catalina > startup.sh and shutdown.sh scripts. See "man kill". > > Regards, > > -- Rodney > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
