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=38403>. 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=38403 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-05 19:00 ------- short update: I'm still trying to hunt it down. here's a short summary: Currently not reproducable at will, but steadily recurring about once a day. As long as I did close looks at it, there are always 2 threads with similar stack trace ( ap_proxy_http_process_response, one ap_proxy_read_headers, the other just ap_getline ). While one is cleaning up, the other is probably stuck in BRIGADE_NORMALIZE (which also does some cleanup). Sounds like a race condition where 2 threads are cleaning up the same brigade. (I will try to get some info on the brigade that the other thread tries to cleanup, next time). step/next did not return the last time, so the MACRO line was never left. the strace close(-1) threads does only show up 1 in 10 times. Either its a different bug or it is about the repeated cleanup/normalization of a socket-bucket. Most of the times the threads produce no system/library calls, so I guess they are caught in a very small loop. -- 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]
