We were helping a client push more data through their apache/tomcat web application running on a Solaris box and decided to switch from the process (prefork) to the threaded(worker) processing model. When we fired up the new apache we started getting errors like these:
[emerg] (45)Deadlock situation detected/avoided: apr_proc_mutex_lock failed. Attempting to shutdown process gracefully.
Not good. After a little digging we found that the default AcceptMutex switched from pthread to fcntl between apache 2.0.49 and 2.0.52.
Adding:
AcceptMutex pthread
to httpd.conf cleared up the errors and we’ve had smooth sailing ever since.
1
Thanks so much for this information! I was getting all kinds of these errors after moving to worker mode on the T1000 platform, and they are cleared up.
BTW, I am running apache 2.2.3.
2
Hi,
i am using apache 2.2.3 and it is running in pre fork mode,
please let me know the config changes to be done to make it run in worker mode.
response will be highly appreciated.
Thanks
Dileepa