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
