This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
hello all, this is very urgent, the customer is getting mad. I can not startup my tomcat server, I think the problem was that when I shutdown the server, it was not shutdown properly, so when I start use startup.sh. it gives me address already in use error. I think I killed all the ps, by useing kill -9, but still I can not start up the server. What is the cleanest way to shutdown and start the tomcat3.3?? Please help, indeed very urgent, I do not know how to talk with my boss for now... thanks.
I don't think the shutdown scripts for Tomcat are very trustworthy - I've seen indications that there were spare Tomcats still running even when I've been scrupulous about shutting down and starting up. The problem is that the standalone server returns before shutdown is complete and the PID file is being removed prematurely (or something that looks like that). A crude but effective way to kill the cats is to do a "ps --width 300 ax | grep omcat" and kill the top process on the list. When it goes down it will take its children with it. I sometimes find 3 or 4 cats, so if after a reasonable delay there's still a Tomcat listed by ps, repeat as needed. The "--width 300" is because on my system, the part of the process status that I grep on is truncated unless I tell ps to format very long lines.
Customer surveys are for companies who didn't pay proper attention to begin with.