DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39914>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39914 ------- Additional Comments From [EMAIL PROTECTED] 2006-06-27 19:58 ------- Generally this works. I assume you are using the worker MPM and a 32Bit Linux? If the lock could not be initialized correctly, we would expect at least one of the following messages with levels: mod_jk: could not init JK log lock in child (ERROR) mod_jk: could not create jk_log_lock (CRITICAL) mod_jk: Could not set permissions on jk_log_lock; check User and Group directives (CRITICAL) Any of these in you mod_jk-Log? Just to make sure, could you also give the exact messages from the failed lock/unlock. Concerning ap_log_rerror: you are right, I will correct to ap_log_error for the upcoming 1.2.16. As always: any chance to test with 2.0.58 and Subversion HEAD of mod_jk? Finally: Could you provide the following things form inside your Apache home: bin/httpd -V include/apr.h include/apr.h -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
