|Anonymous | Login | Signup for a new account||02-16-2019 23:57 PST|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004529||[Resin]||minor||always||04-01-11 10:04||05-17-11 10:01|
|Summary||0004529: mod_caucho threading issue|
(rep by remkodev)
See http://forum.caucho.com/showthread.php?t=27741 [^]
The thread's last resin function is cse_free_lock
cse_free_lock(config_t *config, void *vlock)
After some research, it appears that apr_thread_mutex_destroy(vlock); is not thread safe.
We figured that because our webservers uses multiple resin servers (around 6) in each vhost/apache instance these will cause the race condition over the thread_mutex_destroy method.
Today I altered the configuration of the most busy app ( Note: 0000090% off the hits) to be proxied to a seprate webserver with only 1 resin host configured. This setup did not cause a single hanging process for over 4 hours.
|There are no notes attached to this issue.|
|04-01-11 10:04||ferg||New Issue|
|05-17-11 10:01||ferg||Assigned To||=> ferg|
|05-17-11 10:01||ferg||Status||new => closed|
|05-17-11 10:01||ferg||Resolution||open => fixed|
|05-17-11 10:01||ferg||Fixed in Version||=> 4.0.19|
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
32 total queries executed.|
29 unique queries executed.