client denied by server: index.jsp

Greetings folks,

I usually don't have a problem with apache and apache2 by itself and
with tomcat by itself.

At the moment, before I even try to get an application to run, I'm
simply trying to get the /admin page to default to index.jsp.


Let me back up, after all if you are going to be able to help, you
need some background.

Here is what I'm working with: apache 2.0.52, tomcat 4.1.31, mod_jk
1.2.6

First, I'd like to comment that when searching the newsgroup archives,
I saw a similar subject, but the answer that the original person came
up with did not make since to me.


Apache directive

"DirectoryIndex index.html index.html.var index.jsp index.htm"

Also in the same file, at the end, I have.

"Include /usr/local/tomcat/conf/mod_jk_not_auto.conf"

Originally the above file was auto generated by tomcat, yes I did
follow the directions, what little that do exist. However, if you
want to make changes to the this file, I found that you don't want to
keep the file in the auto subdirectory. I am certainly willing to
point apache back to the original file, if necessary.

Looking in the mod_jk config file. I do see references to

JkMount /admin/j_security_check ajp13
JkMount /admin/*.do ajp13
JkMount /admin/*.jsp ajp13



In fact, currently I can access the directory, however, the index.jsp
does not automatically come up. (I do want the index file to
automatically load). I can select the index.jsp, or login jsp, and
login to the tomcat admin page, which illustrates that the connector
seems to be feeding java requests to tomcat for processing.


The error I'm receiving in apache is:

[Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
denied by server configuration:
/usr/local/tomcat/server/webapps/admin/
WEB-INF/index.html
[Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
denied by server configuration:
/usr/local/tomcat/server/webapps/admin/
WEB-INF/index.htm
[Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
denied by server configuration: index.jsp
[Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
denied by server configuration:
/usr/local/tomcat/server/webapps/admin/
WEB-INF/index.html.var


The file permissions on the page seem fine. User www, in this case,
owns the related files, and the files are readable across the board.


I can feed log files into the group, however, in the past when folks
have dumped logs into a group, with out a request, my interest in
helping goes down.



If someone could point me in the right direction, I would be
appreciative.



Sincerely,



Stan

On 2005-01-12, Stan <hornyaks@mail.nichd.gov> wrote:
> Here is what I'm working with: apache 2.0.52, tomcat 4.1.31, mod_jk
> 1.2.6

You should use mod_jk 2, that is designed for Apache 2.

> The error I'm receiving in apache is:
> [Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
> denied by server configuration:

If the connector was working correctly you shouldn't receive those
messages in the Apache log, since the whole request should be directed
to TomCat. It looks to me that the problem is in the connector or in
the configuration of the connector.

> If someone could point me in the right direction, I would be

I'd start with upgrade to mod_jk2. Pay attention because most of the
documentation for jk2 is a bad copy of jk1 BUT there are many differences
between the two. Specifically the name of the configuration file for
jk2 is HARCODED into jk2 itself and can't be changed (!).

Davide

--
Linux: Because rebooting is for adding new hardware

On 12 Jan 2005 18:34:11 GMT, Davide Bianchi
<davideyeahsure@onlyforfun.net> wrote:

>On 2005-01-12, Stan <hornyaks@mail.nichd.gov> wrote:
>> Here is what I'm working with: apache 2.0.52, tomcat 4.1.31, mod_jk
>> 1.2.6
>
>You should use mod_jk 2, that is designed for Apache 2.
>
>> The error I'm receiving in apache is:
>> [Wed Jan 12 10:50:55 2005] [error] [client 156.40.88.150] client
>> denied by server configuration:
>
>If the connector was working correctly you shouldn't receive those
>messages in the Apache log, since the whole request should be directed
>to TomCat. It looks to me that the problem is in the connector or in
>the configuration of the connector.
>
>> If someone could point me in the right direction, I would be
>
>I'd start with upgrade to mod_jk2. Pay attention because most of the
>documentation for jk2 is a bad copy of jk1 BUT there are many differences
>between the two. Specifically the name of the configuration file for
>jk2 is HARCODED into jk2 itself and can't be changed (!).
>
>Davide

Davide,

I guess the primary reason for not using JK2 is listed on the
following web site:

http://jakarta.apache.org/tomcat/connectors-doc/

Toward the end of the document you will see the following:

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

15 November 2004 - JK2 is officially unsupported!
JK2 has been put in maintainer mode and no further development will
take place. The reason for shutting down JK2 development was the
lack of developers interest. Other reason was lack of users interest
in adopting JK2, caused by configuration complexity when compared to
JK.

JK2 will have it's successor within core Apache2.1/2.2 distribution.
We have developed new proxy_ajp that is an addition to the mod_proxy
and uses Tomcat's AJP protocol stack. It is developed in httpd-2.1 and
integrated in it. We have also developed a new proxy_balancer module
for load balancing http and ajp protocol stacks.

JK will be fully supported for all other web servers. The next JK
release is planned for the end of November. Lots of code from JK2 has
been ported to JK


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

I suppose I could still try jk2. I did download the latest copy
available (15 Nov).


If I see a difference, I'll use JK2 until Apache 2.1 comes out.


Sincerely,


Stan

On 2005-01-13, Stan <hornyaks@mail.nichd.gov> wrote:
> 15 November 2004 - JK2 is officially unsupported!
> lack of developers interest. Other reason was lack of users interest
> in adopting JK2, caused by configuration complexity when compared to
> JK.

Well... I'd say DOH!...

Davide

--
We are not gentle tolerant people. We like drastically effective solutions.
--Steve VanDevender

On 13 Jan 2005 14:44:11 GMT, Davide Bianchi
<davideyeahsure@onlyforfun.net> wrote:

>On 2005-01-13, Stan <hornyaks@mail.nichd.gov> wrote:
>> 15 November 2004 - JK2 is officially unsupported!
>> lack of developers interest. Other reason was lack of users interest
>> in adopting JK2, caused by configuration complexity when compared to
>> JK.
>
>Well... I'd say DOH!...
>
>Davide

I'm full of DOH's myself. However, I think that if anyone, else,
reads these things, that they should be aware of the issue.


Speaking of DOH's, now I'm really revealing my ignorance concerning
the JK2 connector. Maybe one day some one will write some better
documentation for the connector.

Did the ./configure --with-apxs2=/usr/local/apache2/bin/apxs
make
and the /usr/local/apach2/bin/apxs -n jk2 -i mod_jk2.so

Only the mod_jk2.so ended up in the modules directory. ??

OK, so I add the LoadModule jk2_module
/usr/local/apache2/modules/mod_jk2.so in the httpd.conf file. I added
the example stuff to the /usr/local/tomcat/conf/jk2.properties file.

Basically:

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

# Define the communication channel
[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
tomcatId=localhost:8009

# Map the Tomcat examples webapp to the Web server uri space
[uri:/examples/*]
info=Map the whole webapp

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


Start up tomcat and apache2 and get the following in my error_log

-----------------------------------------------------------------
[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
factory for [worker.list] (null)
[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
worker.list
[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
factory for [worker.ajp13.port] (null)
[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
worker.ajp13.port
[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
factory for [worker.ajp13.host] (null)
[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
worker.ajp13.host
[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
factory for [worker.ajp13.type] (null)
[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
worker.ajp13.type
-----------------------------------------------------------------

And in my catalina.out

INFO: APR not loaded, disabling jni components: java.io.IOException:
java.lang.UnsatisfiedLinkError: no jkjni in java.library.path
Jan 13, 2005 11:14:19 AM org.apache.jk.server.JkMain start

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

My feeling is if I can get one directory working, I just need to clone
from the working example.


Ok, I'm obviously missing a few things.


Thanks for the help so far.



Stan

On Thu, 13 Jan 2005 12:28:42 -0500, Stan <hornyaks@mail.nichd.gov>
wrote:

>On 13 Jan 2005 14:44:11 GMT, Davide Bianchi
><davideyeahsure@onlyforfun.net> wrote:
>
>>On 2005-01-13, Stan <hornyaks@mail.nichd.gov> wrote:
>>> 15 November 2004 - JK2 is officially unsupported!
>>> lack of developers interest. Other reason was lack of users interest
>>> in adopting JK2, caused by configuration complexity when compared to
>>> JK.
>>
>>Well... I'd say DOH!...
>>
>>Davide
>
>I'm full of DOH's myself. However, I think that if anyone, else,
>reads these things, that they should be aware of the issue.
>
>
>Speaking of DOH's, now I'm really revealing my ignorance concerning
>the JK2 connector. Maybe one day some one will write some better
>documentation for the connector.
>
>Did the ./configure --with-apxs2=/usr/local/apache2/bin/apxs
>make
>and the /usr/local/apach2/bin/apxs -n jk2 -i mod_jk2.so
>
>Only the mod_jk2.so ended up in the modules directory. ??
>
>OK, so I add the LoadModule jk2_module
>/usr/local/apache2/modules/mod_jk2.so in the httpd.conf file. I added
>the example stuff to the /usr/local/tomcat/conf/jk2.properties file.
>
>Basically:
>
>-------------------------------------------------------------
>
># Define the communication channel
>[channel.socket:localhost:8009]
>info=Ajp13 forwarding over socket
>tomcatId=localhost:8009
>
># Map the Tomcat examples webapp to the Web server uri space
>[uri:/examples/*]
>info=Map the whole webapp
>
>-------------------------------------------------------------
>
>
>Start up tomcat and apache2 and get the following in my error_log
>
>-----------------------------------------------------------------
>[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
>factory for [worker.list] (null)
>[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
>worker.list
>[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
>factory for [worker.ajp13.port] (null)
>[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
>worker.ajp13.port
>[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
>factory for [worker.ajp13.host] (null)
>[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
>worker.ajp13.host
>[Thu Jan 13 11:14:22 2005] [error] env.createBean2(): Error getting
>factory for [worker.ajp13.type] (null)
>[Thu Jan 13 11:14:22 2005] [error] config.update(): Can't create
>worker.ajp13.type
>-----------------------------------------------------------------
>
>And in my catalina.out
>
>INFO: APR not loaded, disabling jni components: java.io.IOException:
>java.lang.UnsatisfiedLinkError: no jkjni in java.library.path
>Jan 13, 2005 11:14:19 AM org.apache.jk.server.JkMain start
>
>-----------------------------------------------------------------
>
>My feeling is if I can get one directory working, I just need to clone
>from the working example.
>
>
>Ok, I'm obviously missing a few things.
>
>
>Thanks for the help so far.
>
>
>
>Stan


BTW: All I'm after is a workable solution. I think I'm closer to a
solution using the JK connector.

However, If I can get something working with the JK2 connector, I
would appreciate the help.


Sincerely,



Stan