Improvement #36
Apache hangs if a request has been received before spepd has finished starting.
| Status: | Closed | Start: | 10/01/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | Shaun Mangelsdorf | % Done: | 100% |
|
| Category: | SPEP (Apache) | Spent time: | - | |
| Target version: | Apache-SPEP-0.8 | |||
Description
The Apache module will wait indefinitely for spepd to accept its connection and cause the user agent to hang while waiting. If all Apache worker processes/threads are exhausted waiting for spepd to come up, startup will fail as ESOE will be unable to contact the SPEP.
This will cause the startup process to hang for a few minutes while ESOE times out the connection, and can cause an outage of several minutes. After the connection has timed out, ESOE sends back a failure response and users will get an error message in their browser, unlocking all the worker processes/threads.
Suggested solution is to return this error condition any time spepd is unavailable to process requests immediately.
Associated revisions
Revision f2351871dd9e14bb9922dd5198a9add4f2004f14
Further changes to adapt ClientSocket to the new socket api.
We now throw an exception if a socket fails to connect after a certain retry limit (currently hard coded to 0).
Closes #36
History
Updated by Shaun Mangelsdorf 343 days ago
- Tracker changed from Feature to Improvement
Updated by Shaun Mangelsdorf 301 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset f2351871dd9e14bb9922dd5198a9add4f2004f14.