Re: [cobalt-developers] tomcat problems

[Brian Baxter <bbaxter@xxxxxxxxxxxxxxxxx>]

At 05:49 PM 11/25/2001 -0800, you wrote:
>Hi,
>
>I installed the Sun Cobalt Developer Kit for Java and the update off the
>Cobalt Developer Network site and tomcat is pitching a fit.  It won't run
>past a few twitches at the command line and dies with different errors if I
>let it fly by restarting httpd.
>
>Now I'm looking at "java.net.Connection.Exception: Connection refused" if I
>try to start it from /usr/java with bin/startup.sh.  If I run "bin/tomcat.sh
>ant -f conf/test-tomcat.xml client", I get screens of fails and then it says
>that it got built.  Go figure.
>
>If I run /etc/rc.d/init.d/httpd stop and then do a /etc/rc.d/init.d/httpd
>start I now also get the java.net.Connection.exception : Connection refused
>error.  At least I'm now getting the same error if it gets fired up with
>httpd or I comand line it.
>

Definitely use the init.d script to start stop and restart! If you dig
through all of the scripts that are getting executed when you do this, you
will notice that there is an attempt to shutdown Tomcat before there is
ever an attempt to start or restart it. If your Tomcat server isn't running
when it tries to do this, you'll get the Connection refused error
everytime. Ignore it.


>One other thing; it locks up the SSH terminal I'm on to get to my Cobalt as
>it goes through a Removing context pass and it will sit there until I
>control-c it.
>

Did you try hitting enter before you cntrl-c the shell? When I start or
restart Apache/Tomcat from the command line, it will always stop at the end
of the context removed processing -- it's actually done and the server is
running, just hit enter to get the command prompt back not cntrl-c. Once
you get to this point telnet to the port on which your Tomcat install is
listening for connections from Apache (I think 8008 is the default).

You should get a connection. If you do, then Tomcat is listening as it
should and the problem is likely somewhere else. If you don't, make sure
that you are checking the right port # (config'd in web.xml). 

I've had Tomcat 3.2.2 running on a RaQ4 for a couple of months now without
any problems at all. The migration to Tomcat 4.0.1 and mod_webapp, however,
is another story.


~Brian