Tomcat newbee can't get life out of said Cat

[drcode]

Hi, I'm running a Debian Woody Unstable system and am just trying to
get the tiniest, slightest sign of life out of Tomcat, but I am getting
nowhere after beating on it for several hours...

Basically, if I run the following from a vanilla Debian command line:

apt-get update
apt-get upgrade
apt-get install tomcat4
export JAVA_HOME=/usr/lib/kaffe
export JAVA_OPTS="-Dbuild.compiler=kjc"
sh /usr/share/tomcat4/bin/startup.sh


I get the following response from the script:

Using CATALINA_BASE: /usr/share/tomcat4
Using CATALINA_HOME: /usr/share/tomcat4
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp
Using JAVA_HOME: /usr/lib/kaffe

Now I would expect that I would at least get some kind of sign of life
from the standalone Tomcat listener at this point:

lynx http://localhost:8080

*unable to connect to remote host*

I have, of course, tried many addtional things: Installing
apache/struts/etc, installing the tomcat4-webapps example code (which
says that server.xml has a reference to 8080, which I cannot find)
trying to ping every other conceivable port referenced anywhere, 80 ,
8081, 8008, etc. Installing/configuring the official sun java SDK, etc.
etc. etc.

If anyone knows more about this, I would be grateful if you could let
me know which (probably incredibly simple) thing(s) I'm leaving off to
just get my "reality check" code to give some sign of life.
Thanks!

-Conrad Barski

 

[Sudsy]

Hi, I'm running a Debian Woody Unstable system and am just trying to
get the tiniest, slightest sign of life out of Tomcat, but I am getting
nowhere after beating on it for several hours...

Basically, if I run the following from a vanilla Debian command line:

apt-get update
apt-get upgrade
apt-get install tomcat4
export JAVA_HOME=/usr/lib/kaffe
export JAVA_OPTS="-Dbuild.compiler=kjc"
sh /usr/share/tomcat4/bin/startup.sh

You're getting the standard startup messages but Tomcat doesn't seem to
start properly. First check the contents of this file:
/usr/share/tomcat4/logs/stdout.log
Error message should show up there.