Re: Access denied with Apache + Tomcat config

[Tony Stocker]

Paul,

My virtualhost file is automatically generated by Tomcat on startup,
so IT is defining the worker (ajp13) by default.  The problem arose
because the sample workers.properties file doesn't use the same name,
by default, for illustrating how the file is used.  I'm sure there's a
way to change the Jkworker that is automatically generated by the
server on startup so that it will be any name I want, including that
found in the sample workers.properties file.  I just find it a bit
irritating that the default implementations of the two components
don't match up on something simple, yet key, as the worker name.

Seems to be a case of the left-hand developer not keeping up with
changes made by the right-hand developer.  What was really helpful was
the complete lack of any logging that indicated this was the problem. 
As I said I was simply documenting what fixed my problem for the sake
of posterity since after days of searching through archives and google
search results looking for information I ran across many threads that
would state a problem, get some responses, but then never report
whether the problem was ever fixed and if so how.


On Wed, 16 Mar 2005 16:29:47 +0100, Paul Puschmann <[EMAIL PROTECTED]> wrote:
> Tony Stocker wrote:
> > All,
> > 
> > I believe that I found my problem, and for the sake of posterity I'm
> > posting it for the next poor fool who is forced to chase around the
> > web and through books looking for decent documentation.
> > 
> > When I set up Tomcat I copied the sample workers.properties file from
> > the JK source.  However it turns out that the sample file uses the
> > wrong worker name (compared to the name that is automatically
> > generated.)  In my case, the sample file was this:
> > 
> > worker.list=ajp13w
> > 
> > worker.ajp13w.type=ajp13
> > worker.ajp13w.host=localhost
> > worker.ajp13w.port=8009
> > 
> > However, as can be seen in my original post, the conf/auto/mod_jk.conf
> > file wants to use "ajp13".
> > 
> > By changing the workers.properties file to 'ajp13' and NOT 'ajp13w'
> > everything started working.
> > 
> > 
> Since you adresss the worker to use in the JkMount-entry, you should use
> the name of the existing worker in your virtualhost-file. (ajp13w)
> 
> Paul
> 
> 
> -
> 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]

Re: Access denied with Apache + Tomcat config

[Paul Puschmann]

Tony Stocker wrote:
> All,
> 
> I believe that I found my problem, and for the sake of posterity I'm
> posting it for the next poor fool who is forced to chase around the
> web and through books looking for decent documentation.
> 
> When I set up Tomcat I copied the sample workers.properties file from
> the JK source.  However it turns out that the sample file uses the
> wrong worker name (compared to the name that is automatically
> generated.)  In my case, the sample file was this:
> 
> worker.list=ajp13w
> 
> worker.ajp13w.type=ajp13
> worker.ajp13w.host=localhost
> worker.ajp13w.port=8009
> 
> However, as can be seen in my original post, the conf/auto/mod_jk.conf
> file wants to use "ajp13".
> 
> By changing the workers.properties file to 'ajp13' and NOT 'ajp13w'
> everything started working.
> 
> 
Since you adresss the worker to use in the JkMount-entry, you should use
the name of the existing worker in your virtualhost-file. (ajp13w)

Paul


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

Re: Access denied with Apache + Tomcat config

[Tony Stocker]

All,

I believe that I found my problem, and for the sake of posterity I'm
posting it for the next poor fool who is forced to chase around the
web and through books looking for decent documentation.

When I set up Tomcat I copied the sample workers.properties file from
the JK source.  However it turns out that the sample file uses the
wrong worker name (compared to the name that is automatically
generated.)  In my case, the sample file was this:

worker.list=ajp13w

worker.ajp13w.type=ajp13
worker.ajp13w.host=localhost
worker.ajp13w.port=8009

However, as can be seen in my original post, the conf/auto/mod_jk.conf
file wants to use "ajp13".

By changing the workers.properties file to 'ajp13' and NOT 'ajp13w'
everything started working.




On Tue, 15 Mar 2005 12:15:42 -0500, Tony Stocker <[EMAIL PROTECTED]> wrote:
> Hello All,
> 
> I have searched the archives but have been unable to find a solution
> to my problem.

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

Access denied with Apache + Tomcat config

[Tony Stocker]

Hello All,

I have searched the archives but have been unable to find a solution
to my problem.

I am integrating Apache 2.0.52 with Tomcat 5.0.28 using mod_jk 1.2.8
(compiled from source).  My client wants to continue using Apache as
the web server due to security and ease of configuration issues, so
using Tomcat as the web server is *not* an option.

The configuration appears to be good, and I can load a page such as
loading {server}/servelets-examples.  However I get "500 Interal
Server Error" whenever I try to launch any of the jsp files.  There is
no indication of error in the CATALINA/logs files.  The only
indication in the Apache log files (error_log) occurs when attempting
to load the initial index.jsp page of a context:
[Tue Mar 15 16:10:23 2005] [error] [client xxx.xxx.xxx.xxx] client
denied by server configuration: index.jsp

I have checked my httpd.conf file and the
CATALINA/conf/auto/mod_jk.conf file but can find no reason why access
to the *jsp is denied.

I can include full versions of my various files, but for the sake of
space I'm only going to include snippets here:

[Apache httpd.conf]
LoadModule jk_module modules/mod_jk.so
...
Include /usr/local/tomcat/conf/auto/mod_jk.conf

[Tomcat conf/auto/mod_jk.conf]
JkWorkersFile "/usr/local/tomcat/conf/jk/workers.properties"
JkLogFile "/usr/local/tomcat/logs/mod_jk.log"
...
 machine2.sample.com:/servlets-examples 

# Static files 
Alias /servlets-examples
"/usr/local/jakarta-tomcat-5.0.28/webapps/servlets-examples"


Options Indexes FollowSymLinks
DirectoryIndex index.html index.htm index.jsp 



# Deny direct access to WEB-INF and META-INF
#

AllowOverride None
deny from all



AllowOverride None
deny from all


JkMount /servlets-examples/jsp/security/protected/j_security_check  ajp13
JkMount /servlets-examples/servlet/HelloWorldExample  ajp13
JkMount /servlets-examples/servlet/SessionExample  ajp13
JkMount /servlets-examples/servlet/RequestHeaderExample  ajp13
JkMount /servlets-examples/servlet/RequestParamExample  ajp13
JkMount /servlets-examples/servlet/CookieExample  ajp13
JkMount /servlets-examples/*.jspx  ajp13
JkMount /servlets-examples/CompressionTest  ajp13
JkMount /servlets-examples/*.jsp  ajp13
JkMount /servlets-examples/servlet/RequestInfoExample/*  ajp13

[Tomcat server.xml]


...




Help greatly appreciated.

Tony

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

Re: Apache / Tomcat Config?

[Steven Gollery]

In server.xml, there's a commented out Context line that sets the path 
of URLS that have a path of "" to go to the ROOT directory. This is 
commented out because it isn't needed: ROOT, as you say, is the default. 
But if you uncomment that and change docBase="ROOT" to docBase="mysite", 
you should get what you want. If "mysite" is not in the webapps 
directory, you can give the full path (or a path relative to "webapps"), 
and tomcat should automatically use whatever directory you put there.

Hope that helps.

Steve Gollery
[EMAIL PROTECTED]


[EMAIL PROTECTED] wrote:

Can someone tell me how to configure apache 2.x with tomcat
4.x so that when someone goes to my site "www.mysite.com"
it automatically looks under the tomcat webapps directory
for a subdirectory called "mysite" to load the index page?

I can't get apache (or tomcat?) to work that way unless I
put my webapp under the ROOT directory.

Thanks.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 






--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Apache / Tomcat Config?

[Turner, John]

Not sure what you are asking here...as far as I know, putting your webapp as
the ROOT is exactly what you should do, as ROOT is the default webapp.

What is it about putting your webapp under the ROOT directory that you don't
like?  Are you asking for a way to have it be the "root" webapp, but not
have to actually put your application's files under the ROOT directory?

John


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:dmaloy@;provide.net]
> Sent: Sunday, October 27, 2002 1:18 PM
> To: [EMAIL PROTECTED]
> Subject: Apache / Tomcat Config?
> 
> 
> Can someone tell me how to configure apache 2.x with tomcat
> 4.x so that when someone goes to my site "www.mysite.com"
> it automatically looks under the tomcat webapps directory
> for a subdirectory called "mysite" to load the index page?
> 
> I can't get apache (or tomcat?) to work that way unless I
> put my webapp under the ROOT directory.
> 
> Thanks.
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:tomcat-user-help@;jakarta.apache.org>
> 

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Apache / Tomcat Config?

[dmaloy]

Can someone tell me how to configure apache 2.x with tomcat
4.x so that when someone goes to my site "www.mysite.com"
it automatically looks under the tomcat webapps directory
for a subdirectory called "mysite" to load the index page?

I can't get apache (or tomcat?) to work that way unless I
put my webapp under the ROOT directory.

Thanks.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Problem in Apache /Tomcat Config

[Suresh Rangarajan]

hi ..
  I am trying to configure Tomcat 3.2.1 to work with Apache 1.3.19 using
mod_jk.
In tomcat we have a servlet mapping called some "intra" ie. URI is
http://localhost:8008/intra which actually points to a servlet.
But Apache does not recognize the servlet and searches for a file called
intra in the docroot of the context.
isn't there any other way other than giving /servlet for a servlet to be
recognized by Apache.

Thanx in advance

Regards,
Suresh.R


--
To unsubscribe:   
For additional commands: 
Troubles with the list: