Re: /context not working -- mod_jk error: no match for /server-status

2009-09-08 Thread Dennis Christopher
Rainer, I've disabled mod_status in the httpd.conf and now the error no longer appears in mod_jk.log. I try http://localhost/sample/ on the server, as you request, and I am back to file not found. I can reach the server from outside - the default web page shows up okay and references

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-07 Thread Rainer Jung
On 04.09.2009 16:01, Dennis Christopher wrote: Rainer, Apparently apache is calling /server-status - I see that mod_status is No, apache itself isn't calling anything. enabled in httpd.conf and exercises that context. One of the frustrations, and I dont know Apache well, is that the

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-04 Thread Dennis Christopher
Rainer, Apparently apache is calling /server-status - I see that mod_status is enabled in httpd.conf and exercises that context. One of the frustrations, and I dont know Apache well, is that the access log seldom updates. The error log in the same folder does update, but contains little

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Rainer Jung
On 03.09.2009 20:24, Dennis Christopher wrote: Rainer, Trying your /sample/ I get the same result. The log appears to respond to that try but the lines are similar to those I originally posted from mod_jk.log. It's as though every context request is translated into '/server-status'.

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Rainer Jung
On 02.09.2009 21:45, Dennis Christopher wrote: Rainer, Thanks for the reply. I was confused in my orginal post: I am not using JBoss at all, only mod_jk. The file contents are as follows below. Apache has a hosts directory, but I'm not sure if the files matter. They are either the

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Dennis Christopher
Rainer, I am not sending /server-status explicitly. The mod_jk log which I excerpted earlier shows the processing of server-status before any context is asked for, apparently when Tomcat starts up. The log continues to repeat these entries - apparently mod_jk is looping trying to

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Rainer Jung
On 03.09.2009 15:34, Dennis Christopher wrote: Rainer, I am not sending /server-status explicitly. The mod_jk log which I excerpted earlier shows the processing of server-status before any context is asked for, apparently when Tomcat starts up. The log continues to repeat these entries

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Dennis Christopher
Rainer, The problem is that I am trying to support simple references to my context without the tomcat port explicitly included. example: myexample.com/sample should invoke the web-app sample. what happens instead: the browser tells me: file not found. looking at catalina.out it seems the

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Rainer Jung
On 03.09.2009 19:15, Dennis Christopher wrote: The problem is that I am trying to support simple references to my context without the tomcat port explicitly included. example: myexample.com/sample should invoke the web-app sample. You don't have a JkMount for /sample, only one for /sample/*.

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-03 Thread Dennis Christopher
Rainer, Trying your /sample/ I get the same result. The log appears to respond to that try but the lines are similar to those I originally posted from mod_jk.log. It's as though every context request is translated into '/server- status'. the bracketed numbers are: [221:268597152]

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-02 Thread Rainer Jung
On 27.08.2009 15:45, Dennis Christopher wrote: environment: Tomcat 6.0.18 under apache2 on Mac OS X Server 10.5 (Leopard). I am using a mod_jk connector with JBoss. I am having trouble getting context urls of the form website.my.com/myapplication honoured (or even localhost/myapplication).

Re: /context not working -- mod_jk error: no match for /server-status

2009-09-02 Thread Dennis Christopher
Rainer, Thanks for the reply. I was confused in my orginal post: I am not using JBoss at all, only mod_jk. The file contents are as follows below. Apache has a hosts directory, but I'm not sure if the files matter. They are either the apache .default files or slight modifications of

RE: /context not working -- mod_jk error: no match for /server-status

2009-08-27 Thread Martin Gainty
JBOSS ajp connector is org.mortbay.http.ajp.AJP13Listener from jboss docs you will need to config jboss-service.xml 5. In jboss_home/server/all/deploy/jbossweb.sar/META-INF/jboss-service.xml, edit the following: - Under the Configure the Request Listeners section, look for the add listener

Re: /context not working -- mod_jk error: no match for /server-status

2009-08-27 Thread Dennis Christopher
Martin, Thanks for the reply. I can't be 100% sure, but I have another setup machine that used to work but the internet serving on it is broken. The config files on it ought to be accurate. However there is no boss-service.xml file on it. In workers.properties, I have defined: