Re: How to put restrictions to mod_jk's log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/23/2010 8:42 PM, Yu Kikuchi wrote: I'm using JkMount in some Virtual Hosts as below. [httpd.conf] Listen 8108 VirtualHost XXX.XXX.19.40:8108 ： JkMount /xxx_api/* worker1 ： /VirtualHost I'm surprised that OPTIONS * HTTP/1.1 routes this request to mod_jk: it doesn't seem to match the pattern. Or, does mod_jk simply observe the request and complain about the URL even though it's not handling it? When I tried to set JkUnmount * worker1, such message printed out and Apache was failed to start. Syntax error on line 425 of /opt/httpd/conf/httpd.conf: JkUnMount context should start with / That's not surprising: * is not a valid pattern. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0Y/R4ACgkQ9CaO5/Lv0PCLjQCgtnyOnfFRLJwERJtS5+q/9v9H cLoAnjBLyQgF9TwE858Voex/I3MJlBpT =Jiz/ -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to put restrictions to mod_jk's log
Mr.Schultz, I'm using JkMount in some Virtual Hosts as below. [httpd.conf] Listen 8108 VirtualHost XXX.XXX.19.40:8108 ： JkMount /xxx_api/* worker1 ： /VirtualHost When I tried to set JkUnmount * worker1, such message printed out and Apache was failed to start. Syntax error on line 425 of /opt/httpd/conf/httpd.conf: JkUnMount context should start with / Best regards, (2010/12/23 2:17), Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/21/2010 11:42 PM, Yu Kikuchi wrote: I also think it's not good idea to make JkLogLevel ERROR. I'll consider to use rotatelogs. You might miss important information if setting to ERROR. Good luck. BTW, I think it's reasonable for apache to send requests of OPTIONS * HTTP/1.0 to kill child processes. Sure, it's reasonable for Apache httpd to send OPTIONS * to it's own processes, just not to mod_jk. But it isn't quite convincing that mod_jk makes those request to WARNING. You really should change your JkMounts so that mod_jk doesn't even see the request. I'm going to inform this matter to bugzilla. I'm sure it will be closed as INVALID unless you do some work to show us that it's actually necessary. Please post your JkMounts. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0SMrkACgkQ9CaO5/Lv0PByvgCgkp3laovx8GQ3S3GL5Ttvj1nu v+0AoLmO8UXQ5tBynMS3EgGaDibOCiGj =5VZu -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to put restrictions to mod_jk's log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/21/2010 11:42 PM, Yu Kikuchi wrote: I also think it's not good idea to make JkLogLevel ERROR. I'll consider to use rotatelogs. You might miss important information if setting to ERROR. Good luck. BTW, I think it's reasonable for apache to send requests of OPTIONS * HTTP/1.0 to kill child processes. Sure, it's reasonable for Apache httpd to send OPTIONS * to it's own processes, just not to mod_jk. But it isn't quite convincing that mod_jk makes those request to WARNING. You really should change your JkMounts so that mod_jk doesn't even see the request. I'm going to inform this matter to bugzilla. I'm sure it will be closed as INVALID unless you do some work to show us that it's actually necessary. Please post your JkMounts. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0SMrkACgkQ9CaO5/Lv0PByvgCgkp3laovx8GQ3S3GL5Ttvj1nu v+0AoLmO8UXQ5tBynMS3EgGaDibOCiGj =5VZu -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to put restrictions to mod_jk's log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/20/2010 10:26 PM, Yu Kikuchi wrote: My Environment: Apache 2.2.11 mod_jk 1.2.30 When my system is highly-loaded, the messeges are printed in mod_jk.log. [mod_jk.log] [Tue Dec 21 11:31:25.958 2010] [4744:3086915888] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / I don't want to print out the warning messages on mod_jk.log. Would you tell me how to restrict them? If you use JkLogLevel, you'll have to set it to ERROR, which I wouldn't recommend: INFO is probably the best setting. PS. I assume the messages are caused by Internal Dummy Connection of Apache by reading access_log. [access_log] ::1 - - [21/Dec/2010:11:31:25 +0900] OPTIONS * HTTP/1.0 200 - Maybe you should make sure that requests to * don't get sent to mod_jk. Maybe something like this: JkUnmount * What do your existing JkMount statements look like? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0RBnMACgkQ9CaO5/Lv0PBQXgCgokD0S9r0DYzrwQ1+/QJHZRUk khIAniRvbhdtcSgcgWsU3fy3SEbC83PR =tzHf -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to put restrictions to mod_jk's log
On 21.12.2010 20:56, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/20/2010 10:26 PM, Yu Kikuchi wrote: My Environment: Apache 2.2.11 mod_jk 1.2.30 When my system is highly-loaded, the messeges are printed in mod_jk.log. [mod_jk.log] [Tue Dec 21 11:31:25.958 2010] [4744:3086915888] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / I don't want to print out the warning messages on mod_jk.log. Would you tell me how to restrict them? If you use JkLogLevel, you'll have to set it to ERROR, which I wouldn't recommend: INFO is probably the best setting. Seconded. But you can add rotatelogs to JkLogFile 8in the same way one does it for Customlog), which at least lets you compress and purge the files in regular intervals (after being rotated). Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: How to put restrictions to mod_jk's log
Mr.Schultz, Mr.Jung Thank you for your advices. I also think it's not good idea to make JkLogLevel ERROR. I'll consider to use rotatelogs. BTW, I think it's reasonable for apache to send requests of OPTIONS * HTTP/1.0 to kill child processes. But it isn't quite convincing that mod_jk makes those request to WARNING. I'm going to inform this matter to bugzilla. Regards, (2010/12/22 5:04), Rainer Jung wrote: On 21.12.2010 20:56, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kikuchi, On 12/20/2010 10:26 PM, Yu Kikuchi wrote: My Environment: Apache 2.2.11 mod_jk 1.2.30 When my system is highly-loaded, the messeges are printed in mod_jk.log. [mod_jk.log] [Tue Dec 21 11:31:25.958 2010] [4744:3086915888] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / I don't want to print out the warning messages on mod_jk.log. Would you tell me how to restrict them? If you use JkLogLevel, you'll have to set it to ERROR, which I wouldn't recommend: INFO is probably the best setting. Seconded. But you can add rotatelogs to JkLogFile 8in the same way one does it for Customlog), which at least lets you compress and purge the files in regular intervals (after being rotated). Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
How to put restrictions to mod_jk's log
Hello All, My Environment: RHEL 5.3 Apache 2.2.11 mod_jk 1.2.30 JBoss 5.0.0 GA When my system is highly-loaded, the messeges are printed in mod_jk.log. [mod_jk.log] [Tue Dec 21 11:31:25.958 2010] [4744:3086915888] [warn] map_uri_to_worker_ext::jk_uri_worker_map.c (962): Uri * is invalid. Uri must start with / I don't want to print out the warning messages on mod_jk.log. Would you tell me how to restrict them? PS. I assume the messages are caused by Internal Dummy Connection of Apache by reading access_log. [access_log] ::1 - - [21/Dec/2010:11:31:25 +0900] OPTIONS * HTTP/1.0 200 - Regards, - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
