Good Afternoon Michael
The Tomcat ajp connector configuration available at
http://tomcat.apache.org/tomcat-3.3-doc/mod_jk-howto.html
states that when the attribute forwardAll=true ALL requests go to tomcat
to quote the doc
a.. "forwardAll - If true, forward all requests to Tomcat. This helps ensure
that all the behavior configured in the web.xml file functions correctly.
If false, let Apache serve static resources.
The default is true.
Warning: When false, some configuration in the web.xml may not be duplicated
in Apache.
Review the mod_jk conf file to see what configuration is actually being set
in Apache. "
so in the event that forwardAll=true then all your requests will go to
Tomcat
then we can look at the tomcat and specifically the connector directives
available at
http://tomcat.apache.org/connectors-doc/config/apache.html which states
JKUnmount takes precedence over JKMount statement and blocks access to the
url specified in the JkUnMount directive
to quote
"JkUnmount directive acts as an opposite to JkMount and blocks access to a
particular URL. The purpose is to be able to filter out the particular
content types from mounted context. The following example mounts /servlet/*
context, but all .gif files that belongs to that context are not served.
# send all requests ending with /servlet to worker1
JkMount /servlet/* worker1
# do not send requests ending with .gif to worker1
JkUnMount /servlet/*.gif worker1
#JkUnMount takes precedence over JkMount directives, meaning that the JK
will first look for unmount and then for mount directives. The following
example will #block all .gif files.
# do not send requests ending with .gif to worker1
JkUnMount /*.gif worker1
# The .gif files will not be mounted cause JkUnMount takes
# precedence over JkMount directive
JkMount /servlet/*.gif worker1"
To my understanding forwardAll acts as the
gatekeeper to tomcat
Once tomcat has the request tomcat (and specifically
tomcat connectors) directives JKUnMount would then block access to that URL
Anyone else ?
Martin-
----- Original Message -----
From: "Michael Andreas Omerou" <[EMAIL PROTECTED]>
To: "'Martin Gainty'" <[EMAIL PROTECTED]>
Cc: "'Tomcat Users List'" <users@tomcat.apache.org>
Sent: Wednesday, December 14, 2005 10:09 AM
Subject: RE: Problem with mod_jk Connector
Hi Martin,
Thanks for your message and I apologise for the late reply but I have been
so busy with so many other things.
Before I proceed with using forwardAll as you suggested I would like to
ask
you whether using forwardAll will still allow me to use JkUnmount.
Thanks,
Michael
-----Original Message-----
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 11 December 2005 16:11
To: [EMAIL PROTECTED]
Cc: Tomcat Users List
Subject: Re: Problem with mod_jk Connector
Straight from the doc available at
http://tomcat.apache.org/connectors-doc/config/apache.html
forwardAll=true
in your httpd.conf forwards ALL requests to tomcat
JkUnMount takes precedence over JkMount directives, meaning
that the JK will first look for unmount and then for mount
directives. The following example will block all .gif files.
# do not send requests ending with .gif to worker1
JkUnMount /*.gif worker1
# The .gif files will not be mounted cause JkUnMount takes
# precedence over JkMount directive
JkMount /servlet/*.gif worker1so in effect your JkUnmount
statement is blocking access to the parameter following
JkUnmount commandMartin-
----- Original Message -----
From: "Michael Andreas Omerou" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <users@tomcat.apache.org>; "'Martin Gainty'"
<[EMAIL PROTECTED]>
Sent: Sunday, December 11, 2005 3:57 AM
Subject: RE: Problem with mod_jk Connector
Hi Martin,
Below is my entire workers.properties file:
workers.tomcat_home=/usr/local/jakarta/jakarta-tomcat
workers.java_home=/usr/local/j2sdk
ps=/
worker.list=ajp13
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
worker.ajp13.lbfactor=50
worker.ajp13.cachesize=10
worker.ajp13.cache_timeout=600
worker.ajp13.socket_keepalive=1
worker.ajp13.socket_timeout=300
I have set JKLogLevel to info but although the problem
occurs nothing goes
there. In fact even for requests forwarded from Apache to
Tomcat there
are
no entries in mod_jk.log.
Regarding forwardAll I am not aware of this option, where does it go?
Please note that eventually I need to have the JKUnmount in
my httpd.conf.
Thanks,
Michael
-----Original Message-----
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 10 December 2005 23:02
To: [EMAIL PROTECTED]
Cc: 'Tomcat Users List'
Subject: Re: Problem with mod_jk Connector
what this says is that all requests goto ajp13 worker I will
need to see worker.properties file and the value of forwardAll
set JkLogLevel info
Martin-
----- Original Message -----
From: "Michael Andreas Omerou" <[EMAIL PROTECTED]>
To: "'Tomcat Users List'" <users@tomcat.apache.org>;
"'Martin Gainty'"
<[EMAIL PROTECTED]>
Sent: Saturday, December 10, 2005 2:33 PM
Subject: RE: Problem with mod_jk Connector
Hi Martin,
Below is the extract from my httpd.conf:
LoadModule jk_module
modules/mod_jk-1.2.15-solaris8-sparc-apache-1.3.33.so
JkWorkersFile /usr/local/etc/httpd/conf/workers.properties
JkLogFile /usr/local/etc/httpd/logs/mod_jk.log
JkLogLevel error
JkMount /* ajp13
The idea is that all requests (jsp, servlets, images, etc.)
are forwarded
from Apache to Tomcat and this works fine with mod_jk
version 1.2.5. When
I
upgraded to 1.2.15 though the forwards still work but only
if there are no
URL parameters. This is what I cannot understand: if there are URL
parameters then it looks as if Apache tried to serve the
request instead
of
forwarding to Tomcat.
Any help will be much appreciated.
Thanks in advance,
Michael
-----Original Message-----
From: Martin Gainty [mailto:[EMAIL PROTECTED]
Sent: 10 December 2005 17:50
To: [EMAIL PROTECTED]
Cc: users@tomcat.apache.org
Subject: Re: Problem with mod_jk Connector
Michael-
in your httpd.conf we need to see JKMount statement for
handling *.jsp pages see
http://tomcat.apache.org/tomcat-4.1-doc/config/jk.html
e.g.
For example the following directives will send all requests
ending in .jsp or with /servlet as the second path componenet
to the "ajp13" worker, but jsp requests to files located in
/otherworker will go to "remoteworker".
JkMount /*.jsp ajp13
JkMount /*/servlet/ ajp13
JkMount /otherworker/*.jsp remoteworker
Martin------ Original Message -----
From: "Michael Andreas Omerou" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Saturday, December 10, 2005 10:25 AM
Subject: Problem with mod_jk Connector
Hello,
I have a Solaris server where I use Apache and Tomcat and I
connect them
using mod_jk. So far I was using mod_jk 1.2.5 and all
requests to Apache
were forwarded to Tomcat. Then, I needed to host some
things under Apache
(basically web statistics software, webmail, etc.). So I
thought of using
JkUnmount to do this.
JkUnmoun is not supported from mod_jk 1.2.5 so I installed
the latest
version 1.2.15. Now JkUnmount works but I have another problem.
If a url which is meant to be sent to Tomcat contains URL
parameters, e.g.
something like ...../hotelDetails.jsp?hotelCode=AMY, then
the request is
not
forwarded from Apache/Mod_jk.
I checked everywhere for solutions to this but could not
find any.
Your help willl be much appreciated.
Rgds,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-----------------------------------------------------------
----------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
