Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360938 - Connections closed after a while
Summary: Connections closed after a while
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.5.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 7.5.x   Edit
Assignee: Simone Bordet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-14 06:43 EDT by Simone Bordet CLA
Modified: 2011-10-14 07:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Bordet CLA 2011-10-14 06:43:52 EDT 
In Jetty 7.5.2 a mechanism to detect non-progressing connection was added to AsyncHttpConnection, mostly to avoid spin loops.

However, it is possible that from time to time a call to handle() makes no progress, even though previous or successive calls to handle() do make progress.

The counter for _total_no_progress is only incremented and never reset, and this, after a while, causes the connection to be closed even if it is working properly.
Comment 1 Simone Bordet CLA 2011-10-14 07:59:18 EDT 
The counter for _total_no_progress is now reset when some progress is made.