With lsof you can find out which processes listens on a given port. As each tomcat has a unique ip/port combination you can find the pid of the vm for a given tomcat with that.
BTW: the way to use wget is better, as this catches all errors where there might be a process that simply doesn't react to requests (dead locks etc.) The first way we just use to stop all processes for a given site if the standard shutdown of the webserver fails. > -----Ursprüngliche Nachricht----- > Von: camccuk [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 20. März 2002 15:46 > An: Tomcat Users List > Betreff: Re: Figuring out which Unix process is which <snip/> > As I was saying: this is fine until the process gets swapped > out at which point > ps reports the process as [java], no matter how many 'w's you > specify - no one > has been able to tell me a workaround for this. Thus, options > seems to be: > > - killall 0 <pid> although I'm not sure (yet) how to capture TC's pid > - use wget to check the server from a client perspective... <snip/> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
