I don't think that's the best solution. The java.exe which is bound to
8005 is probably your tomcat service
started but not active. From previous emails I assume you are running
under Windows.
Here's a suggestion (you may have tried this)
1. Go to the windows services manager and make sure that tomcat is set
to 'manual start'
2. Reboot the machine.
3. Try the netstat to see if anything is bound to 8005. If so,
investigate exactly what.
4. Start tomcat either from the task bar or the services manager
5. Check the logs to see if it started OK.
I'd guess that it is possible that tomcat was already running but not
responding and when you attempted to start it again you were getting the
'already bound' error message.
Regards
Alan
Ljuba Veselinova wrote:
I have tried to kill java.exe that's listening to port 8005 several
times now without success. How do I assign other ports to either
java.exe or tomcat?
Thanks,
Ljuba
On Dec 14, 2007 2:48 PM, David Smith <[EMAIL PROTECTED]> wrote:
I've also found the TcpDump tool available from Microsoft's website
extremely helpful in looking at this stuff.
I would say it should be safe to stop the instance of java.exe holding
on to 8005, but you should try to be sure it's not used for anything.
Various third party software companies have been known to leverage
tomcat in their own products.
--David
Ljuba Veselinova wrote:
I found info about netstat in the windows help files. I apologize for
this simple question. I'm looking at the results produced by netstat
and tasklist right now.
It looks like java is listening to port 8005; there appear to be two
instances of java.exe running and each one of them is listening to
several ports. I need java to run though. Is it safe to end the
instance of java.exe listening to port 8005?
Ljuba
On Dec 14, 2007 2:03 PM, Markus Schönhaber
<[EMAIL PROTECTED]> wrote:
Ljuba Veselinova wrote:
Apache is running but it uses port 80. As far as I can tell (via the
Task manager panel) there are no other instances of tomcat running on
the machine. How do I check what's running specifically on port 8005?
If you're using XP or better
netstat -ano
will show you which process id listens on what address and port.
Or you could use something like TcpView:
http://www.microsoft.com/technet/sysinternals/Networking/TcpView.mspx
Regards
mks
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
