On Tue, Aug 31, 2010 at 9:06 AM, Alan Holden <[email protected]> wrote:
> I've tried killing all the Tomcat processes and restarting it, no luck. > If the error message is to be believed, that means you still have something running on port 8080. I know, stating the obvious, but I like to start simple. ;-) There's a few approaches to check this: 1. telnet to port 8080 -- if you get a connection, something is listening on that port 2. pgrep tomcat -- maybe there's an auto-starting one that you forgot about? 3. ps -wef | grep tomcat (to check for one that isn't running as a process) 4. run netstat and see if that tells you anything -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
