https://issues.apache.org/bugzilla/show_bug.cgi?id=57520
Bug ID: 57520
Summary: proxy: worker failure disrupts existing connections
Product: Apache httpd-2
Version: 2.2.29
Hardware: PC
OS: Linux
Status: NEW
Keywords: ErrorMessage
Severity: major
Priority: P2
Component: mod_proxy
Assignee: [email protected]
Reporter: [email protected]
Depends on: 37770
I have been stress-testing fault tolerance of an Apache load balancer with
Jetty backend being restarted under heavy load.
Our test requests involve downloading of large XML documents (in HTTP request
bodies) with heavy custom processing before response - which means the full
requests take between 100-1000ms depending of the system load.
Initially, I have been getting errors similar to the ones described in Bug
37770, so I applied all the proposed fixes in all possible combinations (HTTP
1.0, no keepalive, initial not pooled, etc) - however the same errors as in Bug
37770 kept re-appearing from time to time.
Then I noticed that our Jetty servlet occasionally fails to read HTTP input
stream - encountering and logging an early EOF. Seems to me the ONLY possible
cause of this condition would be if httpd forcefully closed the connection for
currently executing requests. This could occur once Jetty has stopped accepting
new requests, but have not yet finished processing existing ones - it would
return an error to httpd, which would mark the worker as failed and kill
existing connections. This condition would be noticeable with large requests
under heavy load.
I wonder if this theory makes sense and if a fix could be developed.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
