httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34332] - apr_socket_send() gives up too easily
Date Mon, 23 May 2005 20:17:49 GMT
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=34332>.
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=34332





------- Additional Comments From trawick@apache.org  2005-05-23 22:17 -------
>There are many reasons that the socket may become
>unwritable again (resource shortages, competing access),

Competing access isn't an issue here.  There is one thread checking for
writability, and no other threads will consume the writeability characteristic.

It seems very odd that an obscure problem such as a resource shortage (lack of
mbufs ?) is the explanation for what is going on, since since this problem is so
easily recreatable for you.

Is there any way to get a syscall trace of the httpd process during the failure
scenario so we can see this explicitly?

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message