You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Bob Marcum <bm...@houston.rr.com> on 2001/11/11 16:54:12 UTC
Bringing up tomcat, reliably.
I am having problems getting tomcat to reliably come up.
I am working in a RedHat Linux 7.1 environment.
Occasionally, tomcat comes up okay. But once it fails to come up, I
struggle to get to come up again. Here is what happens ...
When I execute the startup.sh script the script happily reports its
work. but the catalina.out log indicates failure due to "Address
already in use". Netstat, however, does not report any use of port
8080. (server.xml is set to port 8080 for the http protocol.)
I have tried to change the port number in server.xml to another port,
but that seems to have no effect; I get the same response.
And ... when I try to make a connect to tomcat with the browser by
"http://localhost:8080/", the netscape browser reports "connecting to
..." but then just hangs.
Very frustrating ... because I don't know where to look or what to do
next to solve this problem.
Would it be useful, as a diagnostic technique, to shorten the timeout
value in the server.xml?
Thanks.
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
Re: Bringing up tomcat, reliably.
Posted by Nikola Milutinovic <Ni...@ev.co.yu>.
> Bob:
>
> I can't really comment on Linux, but most Unixes will encumber bound
> ports for a while (read a minute or two) under certain circumstances.
> This could be triggered if Tomcat had open client connections at
> the time of shutdown.
Those sessions should list under "netstat" as CLOSE_WAIT or anything else but ESTABLISHED. Anyway, that never stopped Apache or any other server software from coming up.
Are you sure Tomcat is down? Try "lsof" and see if it mentions either port 8080 or Tomcat (java).
Nix.
Re: Bringing up tomcat, reliably.
Posted by Tom Drake <rt...@pobox.com>.
Bob:
I can't really comment on Linux, but most Unixes will encumber bound
ports for a while (read a minute or two) under certain circumstances.
This could be triggered if Tomcat had open client connections at
the time of shutdown.
----- Original Message -----
From: "Bob Marcum" <bm...@houston.rr.com>
To: <to...@jakarta.apache.org>
Sent: Sunday, November 11, 2001 7:54 AM
Subject: Bringing up tomcat, reliably.
| I am having problems getting tomcat to reliably come up.
|
| I am working in a RedHat Linux 7.1 environment.
|
| Occasionally, tomcat comes up okay. But once it fails to come up, I
| struggle to get to come up again. Here is what happens ...
|
| When I execute the startup.sh script the script happily reports its
| work. but the catalina.out log indicates failure due to "Address
| already in use". Netstat, however, does not report any use of port
| 8080. (server.xml is set to port 8080 for the http protocol.)
|
| I have tried to change the port number in server.xml to another port,
| but that seems to have no effect; I get the same response.
|
| And ... when I try to make a connect to tomcat with the browser by
| "http://localhost:8080/", the netscape browser reports "connecting to
| ..." but then just hangs.
|
| Very frustrating ... because I don't know where to look or what to do
| next to solve this problem.
|
| Would it be useful, as a diagnostic technique, to shorten the timeout
| value in the server.xml?
|
| Thanks.
|
| --
| To unsubscribe: <ma...@jakarta.apache.org>
| For additional commands: <ma...@jakarta.apache.org>
| Troubles with the list: <ma...@jakarta.apache.org>
|
|
|
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>
Re: Bringing up tomcat, reliably.
Posted by Remy Maucherat <rm...@home.com>.
> I am having problems getting tomcat to reliably come up.
>
> I am working in a RedHat Linux 7.1 environment.
>
> Occasionally, tomcat comes up okay. But once it fails to come up, I
> struggle to get to come up again. Here is what happens ...
>
> When I execute the startup.sh script the script happily reports its
> work. but the catalina.out log indicates failure due to "Address
> already in use". Netstat, however, does not report any use of port
> 8080. (server.xml is set to port 8080 for the http protocol.)
Tomcat is also using another port for the shutdown command (8005 by default,
I think). Maybe it's the one causing trouble here.
> I have tried to change the port number in server.xml to another port,
> but that seems to have no effect; I get the same response.
>
> And ... when I try to make a connect to tomcat with the browser by
> "http://localhost:8080/", the netscape browser reports "connecting to
> ..." but then just hangs.
>
> Very frustrating ... because I don't know where to look or what to do
> next to solve this problem.
>
> Would it be useful, as a diagnostic technique, to shorten the timeout
> value in the server.xml?
I've never seen that kind of problems on my Windows.
Tomcat has some stability problem with JDK 1.3 under Linux with recent
GLIBC, where the JVM crashes during the Tomcat startup. It's a JDK bug, and
there is a workaround in the relase notes. Did you correctly set the
appropriate env variables if you're using JDK 1.3 ? You can also upgrade to
1.4 beta 3.
Remy
--
To unsubscribe: <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>