because the Tomcat-Apache Service listens on port 8008 ( see your
server.xml, at the end )
best regards
carlos ferreira
Jeffrey Bonevich wrote:
Why would I do that when Tomcat is listening on 8080?
Actually did a little more research and there is already a bug
registered that covers
09:18
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Configuration problems: mod_webapp with Tomcat 4.0.3 and
Apache 2.0.35
hi,
1) the mod_webapp should connect to localhost:8008 as teh connector is
listeneing on 8008 while tomcat is listening on 8080 for http requests
2
: Configuration problems: mod_webapp with Tomcat 4.0.3 and
Apache 2.0.35
hi,
1) the mod_webapp should connect to localhost:8008 as teh connector is
listeneing on 8008 while tomcat is listening on 8080 for http requests
2) it seems that for the moment one has to provide the correct port to
apache
Try localhost:8008 instead
--Jay Gardner
-Original Message-
From: Jeffrey Bonevich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 18, 2002 5:57 PM
To: [EMAIL PROTECTED]
Subject: Configuration problems: mod_webapp with Tomcat 4.0.3 and Apache
2.0.35
Ok, on to the next set of issues!
Why would I do that when Tomcat is listening on 8080?
Actually did a little more research and there is already a bug
registered that covers this issue.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4042
Looks as though there has been no action on this one for a while, and
now it is very
Regardless, it still does not work. The issue I am concerned with
appears to be a bug - could be in mod_webapp or it could actually be in
the Apache 2 code (server_rec is not getting a port number assigned to
it, even after Listen supplies it).
jeff
Andrew Logan wrote:
I believe the
