Thanks! That makes it usable. I'll keep an eye out for 4.1.33.
-- Rob
On 08/15/2006 07:58 PM, Mark Thomas wrote:
Mark Thomas wrote:
I am now seeing the same thing on my dev box. I'm looking in to it and
will let you know.
My bad. If you use protocolHandler rather than
protocolHandl
Mark Thomas wrote:
> I am now seeing the same thing on my dev box. I'm looking in to it and
> will let you know.
My bad. If you use protocolHandler rather than
protocolHandlerClassName in the AJP connector things should work as
you expect. This is a coding bug rather than a doc bug and is enough
t
Rob Tanner wrote:
> This is the snippet where the connectors are defined. It is identical
> to my older development system and it's pretty much the Tomcat comes out
> of the box (or the tarball):
I am now seeing the same thing on my dev box. I'm looking in to it and
will let you know.
Mark
This is the snippet where the connectors are defined. It is identical
to my older development system and it's pretty much the Tomcat comes out
of the box (or the tarball):
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" />
On 0
Hi Rob,
I'm just curious to know how you manage to access your application
from port 8009 via browser while your Config shows :
worker.ajp13.port=8009
either you specified the wrong port number for the http connector or
you stated the wrong one.
AFAIK the port 8009 is used by mod_jk to communic
Rob Tanner wrote:
> Mark,
>
> The distinction does not appear to be the case. On my old development
> system which does work, I can go via apache or directly to port 8009 and
> they both work.
>
> -- Rob
For this to work, you can't be using port 8009 for the ajp connector
on your dev system. Ca
Rob-
If you have 2 servlets e.g.you have two tomcat running, listning Ajp12 on 10001
and 10002 ports:
Take a look at
/etc/httpd/conf/httpd.conf:
-
LoadModule jk_module /etc/httpd/libexec/mod_jk.so
JkWorkersFile /etc/httpd/conf/workers.properties
Listen 8001
Por
Mark,
The distinction does not appear to be the case. On my old development
system which does work, I can go via apache or directly to port 8009 and
they both work.
-- Rob
Mark Thomas wrote:
Rob Tanner wrote:
Hi,
I'm building a new development system. I can access my applications
dir
Rob Tanner wrote:
> Hi,
>
> I'm building a new development system. I can access my applications
> directly from my browser 0n port 8009, but not through Apache.
If it works through a browser you must have the connector configured
for http. You need to configure it for ajp for it to work with the
Hi,
I'm building a new development system. I can access my applications
directly from my browser 0n port 8009, but not through Apache. I'm have
j2sdk1.4.2_12 and apache-tomcat-4.1.32 installed. The version of Apache
is 2.0.54 (from the FC4 distro). I built the connector from the
tomcat-co
10 matches
Mail list logo
