Apache2 listens to port 80 and Tomcat6 to 8080 by default. I KNOW that
browsing an IP http://xxx.xxx.xxx.xxx takes me to the Apache welcome
page if the Apache service is running irrespective of Tomcat is enabled
or not. If I stop the Apache service I get Unable to connect even if
Tomcat is
Or put Apache 2 in front of your Tomcat, as it is usually done in production
environment.
...and how do I do that?
/dan
On Fri, 2008-02-22 at 16:18 +0100, Antonio Petrelli wrote:
2008/2/22, Hassan Schroeder [EMAIL PROTECTED]:
On Fri, Feb 22, 2008 at 7:08 AM, elvberg [EMAIL PROTECTED] wrote
you can run something like jsvc and
set the user to 'tomcat' which allows you to bind
Howto?
/dan
On Fri, 2008-02-22 at 12:57 -0800, Alan Chaney wrote:
Or as I mentioned in a recent email, you can run something like jsvc and
set the user to 'tomcat' which allows you to bind to the port and
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
I'm running FedoraCore8.x86_64 on a machine placed in a LAN with router
address 195.168.0.135. The Internet static IP address is 87.227.4.194.
So, by hitting http://87.227.4.194 you'll come to the Apache2 welcome
page because there is nothing in /var/www/html.
My question:
Is my tomcat5.5 to be
I have changed in server.xml (as root) to
Connector port=80 protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443 /
!-- A Connector using the shared thread pool--
!--
Connector executor=tomcatThreadPool
port=80 protocol=HTTP/1.1
I see Tomcat's welcome page if I browse http://localhost:8084/ or
http://192.168.0.135:8084
/dan
On Wed, 2008-02-20 at 16:12 -0500, Len Popp wrote:
Does Tomcat work locally on the server? i.e. on the server computer
itself, if you browse to http://localhost/ do you see Tomcat's welcome
page?
, 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