On 12/04/17 21:30, Ruediger Pluem wrote:
A debug build which states the line numbers would be more helpful here. What I
can conclude so far by looking at the
code is that it does not wait on the client to sent something but that it does
wait on the socket to accept data for
sending.
So
>...oh. So errno is actually threadsafe, but its "address" is the same in
>every thread? Interesting.
MT-Safe errno of Solaris is implemented as a function,
so its address is same but the value is different.
cf. https://src.illumos.org/source/xref/illumos-gate/usr/src/head/errno.h
On 12/04/17 21:37, Eric Covener wrote:
Any chance the logs also report write timeouts that precede this? Are
there "similar" threads waiting for writability of actual response
data (e.g. ap_invoke_handler in the stack)
I'm not aware of any write timeouts in the httpd logs but then, this was
a
On 4/12/2017 9:12 PM, William A Rowe Jr wrote:
On Wed, Apr 12, 2017 at 5:31 PM, wrote:
Author: gsmith
Date: Wed Apr 12 22:31:15 2017
New Revision: 1791192
URL: http://svn.apache.org/viewvc?rev=1791192=rev
Log:
Add another include since applink.c has been moved in
the