I saw this same thing just the other day.  It had to do with how we
configured Apache security.  We had moved our JkMounts from one Virtual
Host into the main (:80) section, which had different security
lockdowns(deny from all).  Because of this, Apache was trying to
evaluate the URL first, and then denying it, not giving Tomcat a chance.
  We also saw the mod log messages and never figured out why it was
seemingly successful yet still we got the forbidden:

Now, my case might be a little different than yours.  I was trying to
have apache serve up our static content.  We had the following:

JkMount /nps/webacc/* ajp13
JkMount /nps/webacc ajp13
JkMount /nps/*.jsp ajp13
JkMount /nps/servlet/* ajp13

Alias /nps "SYS:/tomcat/4/webapps/nps"

<Directory "SYS:/tomcat/4/webapps/nps">
    Options Indexes FollowSymLinks
</Directory>

I think we had to change the <Directory> tag to look more like this:

<Directory "SYS:/tomcat/4/webapps/nps">
    Options FollowSymLinks
    Order allow,deny
    Allow from all
</Directory>

This opened back up permissions on just this directory.  Of course,
without the Alias directive things also worked, so I don't know if this
fits your case or not.

-----Original Message-----
From: Manoj Kithany [mailto:[EMAIL PROTECTED]] 
Sent: Friday, February 14, 2003 12:42 PM
To: [EMAIL PROTECTED] 
Subject: Re: Simple WAR on Apache + Tomcat + JBoss


I checked the mod_jk.log file and found following...

--------------------------------------------------------------------
[Fri Feb 14 09:44:47 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Fri Feb 14 09:44:47 2003]  [jk_uri_worker_map.c (477)]: Attempting to
map
URI '/mig/'
[Fri Feb 14 09:44:47 2003]  [jk_uri_worker_map.c
(502)]:jk_uri_worker_map_t::map_uri_to_worker, Found a context match
ajp13
->/mig/
[Fri Feb 14 09:44:51 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Fri Feb 14 09:44:51 2003]  [jk_uri_worker_map.c (477)]: Attempting to
map
URI '/mig/'
[Fri Feb 14 09:44:51 2003]  [jk_uri_worker_map.c
(502)]:jk_uri_worker_map_t::map_uri_to_worker, Found a context match
ajp13
->/mig/
[Fri Feb 14 09:52:43 2003]  [jk_uri_worker_map.c (460)]: Into
jk_uri_worker_map_t::map_uri_to_worker
[Fri Feb 14 09:52:43 2003]  [jk_uri_worker_map.c (477)]: Attempting to
map
URI '/mig/test.jsp'
[Fri Feb 14 09:52:43 2003]  [jk_uri_worker_map.c
(558)]:jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match
ajp13
->*.jsp

---------------------------------------------------------------------

>From the LOG file above it seems that INTEGRATION is successful....
BUT
when
I access http://MY.IP.ADDR.ESS/mig/test.jsp it shows FOLLOWING ERROR
on
BROWSER:--
-----------------------------------------------------------------
Forbidden
You don't have permission to access /mig/test.jsp on this server
-------------------------------------------------------------------

Any guideline on this is appreciated!


>From: "Manoj Kithany" <[EMAIL PROTECTED]>
>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] 
>Subject: Simple WAR on Apache + Tomcat + JBoss
>Date: Fri, 14 Feb 2003 15:29:11 +0000
>
>Hi:
>
>I have a simple WAR file 'mig.war' and want to see if that wokrs on
>Architecture - Apache + JBoss(Tomcat).
>
>I have my mig.war file in /jboss/server/default/deploy
>
>I have my mod_jk.so connector in /usr/local/apache/libexec directory
>
>My httpd.conf has following information at end:
>---------------------------------------------------------
>LoadModule jk_module  libexec/mod_jk.so
>JkWorkersFile /jboss/catalina/conf/jk/workers.properties
>JkLogFile /usr/local/apache/logs/mod_jk.log
>JkLogLevel info
>
>JKMount /examples/servlet/* ajp13
>JKMount /examples/*.jsp ajp13
>
>JKMount /mig/servlet/* ajp13
>JKMount /mig/*.jsp ajp13
>JKMount /mig/* ajp13


Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to