to my earlier report,
I still get sporadic errors:
[Wed Feb 11 14:40:32 2009] [error] (45)Deadlock situation detected/avoided:
apr_global_mutex_lock(jk_log_lock) failed
I also re-ran separate tests with mod_ssl + a plain index.html and observed
consistently that the apache set with mutex to sysvsem
the Apache set to worker mpm I see following error messages in my jk log:
Apache/2.2.11 (Unix) with mod_jk/1.2.26 on Solaris 10.
. . .
[Thu Jan 08 11:42:28 2009] [error] (45)Deadlock situation
detected/avoided:
apr_global_mutex_lock(jk_log_lock) failed
. . .
[Thu Jan 08 11:42:29 2009] [emerg] (45)Deadlock
in my jk log:
Apache/2.2.11 (Unix) with mod_jk/1.2.26 on Solaris 10.
. . .
[Thu Jan 08 11:42:28 2009] [error] (45)Deadlock situation detected/avoided:
apr_global_mutex_lock(jk_log_lock) failed
. . .
[Thu Jan 08 11:42:29 2009] [emerg] (45)Deadlock situation detected/avoided:
apr_proc_mutex_lock
following error messages in my jk log:
Apache/2.2.11 (Unix) with mod_jk/1.2.26 on Solaris 10.
. . .
[Thu Jan 08 11:42:28 2009] [error] (45)Deadlock situation detected/avoided:
apr_global_mutex_lock(jk_log_lock) failed
. . .
[Thu Jan 08 11:42:29 2009] [emerg] (45)Deadlock situation detected/avoided
see following error messages in my jk log:
Apache/2.2.11 (Unix) with mod_jk/1.2.26 on Solaris 10.
. . .
[Thu Jan 08 11:42:28 2009] [error] (45)Deadlock situation
detected/avoided:
apr_global_mutex_lock(jk_log_lock) failed
. . .
[Thu Jan 08 11:42:29 2009] [emerg] (45)Deadlock situation