6825 2009-04-16 13:39:08 +0000 Resource retrieval: no explicit timeout set for HTTP retrievals 2010-09-03 14:00:15 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified Other All RESOLVED FIXED P2 enhancement --- 1 fd abel.rionda oldest_to_newest 24769 0 fd 2009-04-16 13:39:08 +0000 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. 27569 1 fd 2009-09-22 20:52:37 +0000 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. 27574 2 fd 2009-09-22 21:11:57 +0000 Well, the endless loop bug is more on the UI here. See bug 7702. 38453 3 fd 2010-09-03 14:00:15 +0000 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.