One other thought and I don't know how possible this is but it's there
for your consideration. Would you happen to have a connector defined
with the same port number as the shutdown port def.? It wouldn't be
bound until tomcat starts and then either the shudown port or the
connector might bind first, denying the other.
--David
Brian Munroe wrote:
On 8/29/07, Hristian <[EMAIL PROTECTED]> wrote:
How could this be if the port if shows as free on netstat?
Misinterpretation of netstat output? Don't take that the wrong way,
I'm just trying to be helpful. Can you send the output to the mailing
list?
I'd follow Sonal's suggestion, because even though netstat might not
be showing it, the catalina.out log is telling you what is wrong.
Before you change ports, I might trying 'telnet localhost 8005' from a
commandline. If you get connected, issue the command 'SHUTDOWN'
(minus the quotes, ALLCAPS).
If you get connected, but SHUTDOWN doesn't seem to do anything, you
really are using port 8005 for something else.
-- brian
---------------------------------------------------------------------
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]
