|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
ajax
|
|
Issue Links:
|
Reference
|
|
|
|
This issue is related to:
|
|
|
|
|
|
|
|
|
Various reports of frequent HTTP timeouts (generally a 408 is returned to the user). Also, httpd processes can go into an infinite loop on the pool cleanup code. This is directly related to known problems in httpd trunk.
We are waiting for the relevant commits to be reverted in trunk. Then, we will update the ajax instance.
(If the commits haven't been reverted by the evening of 2/29, Justin will revert and apply.)
There are enough important proxy changes that haven't been backported to 2.2.x yet that we should be tracking trunk for a little while.
|
|
Description
|
Various reports of frequent HTTP timeouts (generally a 408 is returned to the user). Also, httpd processes can go into an infinite loop on the pool cleanup code. This is directly related to known problems in httpd trunk.
We are waiting for the relevant commits to be reverted in trunk. Then, we will update the ajax instance.
(If the commits haven't been reverted by the evening of 2/29, Justin will revert and apply.)
There are enough important proxy changes that haven't been backported to 2.2.x yet that we should be tracking trunk for a little while. |
Show » |
|
Bug
Major
issues.apache.org HTTP timeouts and infinite loops
