If you are running on Linux you may have problems using a 'plain' tomcat
installation pointing at port 80. This is a system port and reserved for
privileged access. You must
1. use some kind of redirection such as iptables and leave the tomcat
mapping at 8080
OR
2 you must run tomcat as root THIS IS VERY BAD DON'T DO THIS
OR
3. use something like jsvc and set the 'user' to tomcat after starting
up as root. jsvc will start as root and bind to the port and then
switch to the non-privileged tomcat user for normal operation.
Regards
Alan Chaney
Hassan Schroeder wrote:
On Wed, Feb 20, 2008 at 12:57 PM, elvberg <[EMAIL PROTECTED]> wrote:
I've added to D-Link router Virtual Server List
Name Private IP Protocol Schedule
87.227.4.194 192.168.0.135 TCP 80/80 always
87.227.4.194 192.168.0.135 TCP 8084/8084 always
Why did you feel the need to change this, if you were able to connect
to the instance of httpd before?
And what's the "8084" for?
But as already suggested, make sure that Tomcat's actually running
and can be accessed locally; if not, check your startup logs.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
