This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6825 - Resource retrieval: no explicit timeout set for HTTP retrievals
Summary: Resource retrieval: no explicit timeout set for HTTP retrievals
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Java Library (show other bugs)
Version: unspecified
Hardware: Other All
: P2 enhancement
Target Milestone: ---
Assignee: Abel Rionda
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 13:39 UTC by fd
Modified: 2010-09-03 14:00 UTC (History)
0 users

See Also:

Attachments

Description fd 2009-04-16 13:39:08 UTC 
HttpResourceRetriever does not explicitly define a connection and/or network transmission timeouts. I suspect there is one by default, but it would be better to make it possible to define a timeout in TesterConfiguration.
Comment 1 fd 2009-09-22 20:52:37 UTC 
See Danny's email at:
http://lists.w3.org/Archives/Public/public-mobileok-checker/2009Sep/0005.html

I do not know what the default timeout is, but it gives the impression the mobileOK Checker is running an endless loop when the site fails to respond in a timely fashion.
Comment 2 fd 2009-09-22 21:11:57 UTC 
Well, the endless loop bug is more on the UI here.
See bug 7702.
Comment 3 fd 2010-09-03 14:00:15 UTC 
Explicit timeouts set in HttpResourceRetriever. I took the opportunity to also set the maximum number of concurrent connections to a given host, as default value in Java is 2, while most modern Web browsers use something like 6 concurrent connections.

Settings:
- Connection timeout: 5s
- Socket timeout (send/receive): 30s
- Maximum number of connections per host: 6
- Total number of connections allowed: 60

These settings are hardcoded for the time being. It would be a good idea to be able to set such global configuration settings in some configuration file read by the Checker upon startup, for more flexibility.