Re: Mod_jk fails to connect via ajp13
On 31/07/2011 20:07, Franz wrote: > On the gmane <= 80 chars per line mailing interface I can only offer > my condolences. Why? You choose to use gmane, we didn't. Most folks use plain old e-mail but there are forum like interfaces provided as well. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
Mladen - Thanks a lot. Firstly, I concede that after five years of living in the UK I still can't read and understand Apache manuals. Take, for instance, the subtleties in interpreting the meaning of the noun 'inheritance'. In one sense I thought it means the deceased pass on property to their decendants. Clearly that wasn't the case with mod_jk2. Nor would it seem that in the speak of object oriented languages the superclass itself does not regularly expose the properties that subclasses adopt. Unless, perhaps, in the case of C++ private inheritance. Still, you solved my problem. I had to put in mounts JkMount /myapp/front/* worker1 JkMount /myapp worker1 JkMount /myapp/ worker1 JkMount /myapp/front worker1 JkMount /myapp/front/ worker1 at global level and then add a line JkMountCopy On in virtual hosts. This exposes the servlets at virtual host level but not globally. On the gmane <= 80 chars per line mailing interface I can only offer my condolences. Cheers! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
On 07/31/2011 03:53 PM, Franz wrote: For all I can tell, apache is unaware of any mapping. It looks for the apps under the default doc root. The JkShmFile message I think is no problem, a shared memory file gets created under the apache log directory. You should read the docs before trolling. As explained in the JkMount section [1] By default JkMount entries are not inherited from the global server to other VirtualHosts or between VirtualHosts. For the complete inheritance rules, see: JkMountCopy. I have no problems understanding that, but I'm not the native English speaker. However since it was written by the German guy, I suppose neither you should have ;) Next for mod_jk 'JkMount /foo' != 'JkMount /foo/' If you wish to map both /foo and foo/* you will need two directives or one compound (JkMount /foo|/*) Details are explained in [2] under Uri patterns section. [1] http://tomcat.apache.org/connectors-doc/reference/apache.html [2] http://tomcat.apache.org/connectors-doc/reference/uriworkermap.html Regards -- ^TM - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
Just build and installed mod_jk 1.2.32 from source, but no difference. However, I now find an error message: [Sun Jul 31 16:54:56.635 2011] [14942:139926825768768] [error] init_jk::mod_jk.c (3235): Initializing shm:/etc/apache2/logs/jk-runtime-status.14942 errno=2. Load balancing workers will not function properly. Maybe I should experiment a bit with shm and load balancing, even though I'm not getting why I need load balancing with a single low-traffic server? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
And compiling a jk from source instead using debian dist packages falls on the same? If jk is started and mounts and apache never tries to use mod_jk, 2 main approachs, one as you say, the debian module is broken (sometimes happen in debian, more when are different releases and package versions and dependencies, I assume you did an apt-update and apt-upgrade), second one is apache/workers/vhost misconfig. Hope it helps Enviado desde blackberry -Original Message- From: Franz Date: Sun, 31 Jul 2011 13:53:53 To: Reply-To: "Tomcat Users List" Subject: Re: Mod_jk fails to connect via ajp13 Hi Alexis - Thanks for the answer. For all I can tell, apache is unaware of any mapping. It looks for the apps under the default doc root. The JkShmFile message I think is no problem, a shared memory file gets created under the apache log directory. The jk log file reports a missing uri map though it previously lists them all. The apache access log shows my desperate connection attempts . I still think the module is broken, at least in debian distro. Any way, why do config files for mod_jk need to change completely every two years?? 272 ,1 95% ---> Apache error log. [Sun Jul 31 04:01:27 2011] [notice] caught SIGTERM, shutting down [Sun Jul 31 04:01:28 2011] [warn] No JkShmFile defined in httpd.conf . Using default /var/log/apache2/jk-runtime-status [Sun Jul 31 04:01:28 2011] [warn] No JkShmFile defined in httpd.conf . Using default /var/log/apache2/jk-runtime-status [Sun Jul 31 04:01:28 2011] [notice] Apache/2.2.16 (Debian) mod_jk /1.2.30 PHP/5.3.3-7+squeeze3 with Suhosin-Patch configured -- resuming normal operations [Sun Jul 31 04:01:41 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:41 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 04:01:43 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:43 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 04:01:44 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:44 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 06:25:08 2011] [notice] Graceful restart requested, doing restart apache2: apr_sockaddr_info_get() failed for guppy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
Hi Alexis - Thanks for the answer. For all I can tell, apache is unaware of any mapping. It looks for the apps under the default doc root. The JkShmFile message I think is no problem, a shared memory file gets created under the apache log directory. The jk log file reports a missing uri map though it previously lists them all. The apache access log shows my desperate connection attempts . I still think the module is broken, at least in debian distro. Any way, why do config files for mod_jk need to change completely every two years?? 272 ,1 95% ---> Apache error log. [Sun Jul 31 04:01:27 2011] [notice] caught SIGTERM, shutting down [Sun Jul 31 04:01:28 2011] [warn] No JkShmFile defined in httpd.conf . Using default /var/log/apache2/jk-runtime-status [Sun Jul 31 04:01:28 2011] [warn] No JkShmFile defined in httpd.conf . Using default /var/log/apache2/jk-runtime-status [Sun Jul 31 04:01:28 2011] [notice] Apache/2.2.16 (Debian) mod_jk /1.2.30 PHP/5.3.3-7+squeeze3 with Suhosin-Patch configured -- resuming normal operations [Sun Jul 31 04:01:41 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:41 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 04:01:43 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:43 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 04:01:44 2011] [error] [client 89.247.45.147] File does not exist: /var/www/myapp [Sun Jul 31 04:01:44 2011] [error] [client 89.247.45.147] File does not exist: /var/www/favicon.ico [Sun Jul 31 06:25:08 2011] [notice] Graceful restart requested, doing restart apache2: apr_sockaddr_info_get() failed for guppy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Mod_jk fails to connect via ajp13
as far as i see, I'm not quite expert on mod_jk but I've been using it a lot. This logs shows that the mount occurs. What does apache access and error logs says (also the jk log in debug mode) when you try to reach your mounted apps? On Jul 31, 2011, at 9:08 AM, Franz wrote: >> If you can submit this one, you can submit the mod_jk issue. Give it a try. >> Both works, mod_jk and this list. > >> Kindly and best regards > > Sorry for the two failure/spam messages. I had to write a perl script for the > preformattig and it's not beautiful... > > > --Original Message-- > Hi - > > it's mod_jk time again! I had the module with a jboss/tomcat server > running for years on a debian sarge host with apache 2.0.54/mod_jk2 > and I'm wondering if the module is now called mod_jk again because > it no longer works with debian squeeze/apache 2.2.16. At least the > bug report below seems to indicate just that. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libapache2-mod-jk > ;dist=unstable > > Does it still work? Anyone? Any other apache/mod_jk(2) version I should > try? Seeing that the rather experimental module merely forwards a > couple of requests it has caused me an exceptional amount of headaches > over the years!!! > > The configuration files are all different again from last time: my > old file workers2.properties had mappings > [uri:/myapp/front/*] > and now it seems one has to declare workers in a file workers.properties > > worker.worker1.type=ajp13 > #worker.worker1.host=localhost > worker.worker1.host=127.0.0.1 > worker.worker1.port=8009 > and then put mappings somewhere in the apache config. > > JkMount /myapp/front/* worker1 > > This is what I'm getting this time: > > The poor thing starts off with logging entries, finds the mappings > , reports them 10 times or so and finally, when I try to access the > servlet, it fails. I tried to put the JkMounts inside and outside > virtual host settings, the only difference is that inside a virtual > host the error messages say "no match for myapp/front", outside a > virtual host it's "missing uri map for 127.0.0.1:/myapp/front". > > The tomcat engine is running and ports 8009 and 8080 are open. I can > connect through port 8080 but not 80. > > Any help much appreciated > > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] uri_worker_map_ > add > ::jk_uri_worker_map.c (720): wildchar rule '/myapp/front/*=worker1 > ' source 'JkMount' was added > [...] > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] uri_worker_map_ > dump > ::jk_uri_worker_map.c (186): NEXT (1) map #1: uri=/myapp/front/ > * worker=worker1 context=/myapp/front/* source=JkMount type=Wildchar > len=16 > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] init_jk > ::mod_jk.c (3128): Setting default connection pool max size to 1 > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_read_pro > perty > ::jk_map.c (491): Adding property 'worker.list' with value 'worker1 > ' to map. > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_read_pro > perty > ::jk_map.c (491): Adding property 'worker.worker1.type' with value > 'ajp13' to map. > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_read_pro > perty > ::jk_map.c (491): Adding property 'worker.worker1.host' with value > '127.0.0.1' to map. > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_read_pro > perty > ::jk_map.c (491): Adding property 'worker.worker1.port' with value > '8009' to map. > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_resolve_ > references > ::jk_map.c (774): Checking for references with prefix worker. with > wildcard (recursion 1) > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_shm_calculat > e_size > ::jk_shm.c (132): shared memory will contain 1 ajp workers of size > 320 and 0 lb workers of size 320 with 0 members of size 384+320 > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] do_shm_open > ::jk_shm.c (493): Truncated shared memory to 448 > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] do_shm_open > ::jk_shm.c (538): Initialized shared memory /var/log/apache2/jk-runtime > -status.28302 size=448 free=320 addr=0x7fc1546b4000 > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] do_shm_open_loc > k > ::jk_shm.c (412): Opened shared memory lock /var/log/apache2/jk-runtime > -status.28302.lock > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_dump > ::jk_map.c (589): Dump of map: 'ServerRoot' -> '/etc/apache2' > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_dump > ::jk_map.c (589): Dump of map: 'worker.list' -> 'worker1' > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_dump > ::jk_map.c (589): Dump of map: 'worker.worker1.type' -> 'ajp13' > [Sun Jul 31 03:36:06.418 2011] [28302:140468321695552] [debug] jk_map_dump > ::jk_map.c (58
Re: Mod_jk fails to connect via ajp13
If you can submit this one, you can submit the mod_jk issue. Give it a try. Both works, mod_jk and this list. Kindly and best regards --Original Message-- From: Franz To: users@tomcat.apache.org ReplyTo: Tomcat Users List Subject: Mod_jk fails to connect via ajp13 Sent: Jul 30, 2011 23:16 Hi - I tried to submit a posting for a failing mod_jk but now I see that it is not possible to submit messages here because this mailing interface is even worse than mod_jk. Shame on apache, I should move to IIS. I would never have thought I'd eveer say this. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Enviado desde blackberry - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
