>No - it shows that *something* is listening on 8005, but it's not likely to
be Tomcat. Use the Task Manager to find out what PID 520 is. As I
mentioned before, lots of products have Tomcat embedded in them, and at
least one (VMware) leaves the shutdown port set to the default, creating
difficulty for anyone trying to run an out-of-the-box Tomcat.
>Something *is* using 8005, which will interfere with a Tomcat configured
with the default shutdown port.
>And again, be wary of running Tomcat under Eclipse, since Eclipse likes to
use its own Tomcat configuration, not the one you thing you've set up.
The wierd thing about all of this is whenever I shut my tomcat down then the
127.0.0.1:8005 dissapears from the netstat list. This leads me to believe
that it is Tomcat which is using this. This also leads me to believe there
is something funky with eclipse's setup with Tomcat. Maybe the best
solution is to reinstall it? (I need to use it under eclipse for the
application I am creating JavaServlets/JSPs) If Eclipse uses its own
settings, then how do I make it use Tomcat's or vice versa or is there a
manual on this specific problem with eclipse and Tomcat getting confused
with one anothers configuration settings?
--
View this message in context:
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579543.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
