|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4529 | minor | always | 04-29-11 10:04 | 05-17-11 10:01 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.19 | ||
|
|
|||||
| Summary: | 0004529: mod_caucho threading issue | ||||
| Description: |
(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) { apr_thread_mutex_destroy(vlock); } After some research, it appears that apr_thread_mutex_destroy(vlock); is not thread safe. (https://www.securecoding.cert.org/co...read%27s+mutex) [^] 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |