Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331253 - [api] add timeout to webutil.execute to ensure that connections are not infinite
Summary: [api] add timeout to webutil.execute to ensure that connections are not infinite
Status: RESOLVED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-26 17:00 EST by Shawn Minto CLA
Modified: 2011-04-07 18:14 EDT (History)
0 users

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 Shawn Minto CLA 2010-11-26 17:00:03 EST 
Right now, if the request that is being executed hangs forever and does not respond to cancellation, webutil will continue to wait.  There should be a way to provide a timeout for the length to wait after a cancellation before assuming that it isn't coming back.
Comment 1 Steffen Pingel CLA 2010-12-22 18:53:57 EST 
Shawn, as far as I can tell future.isCancelled() always returns true so the code path that invokes request.get() without a timeout should never be invoked. Can you provide a test case that demonstrates the problem?
Comment 2 Shawn Minto CLA 2011-04-07 18:14:21 EDT 
I can't seem to reproduce the problem that I was having with the original implementation, so marking as invalid.