0004377: CurlResource socket timeouts should pull initial values from JVM system properties

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004377

[Quercus]

major

always

02-07-11 09:01

06-23-12 11:28

Reporter

xerafin

View Status

public

Assigned To

nam

Priority

normal

Resolution

no change required

Status

closed

Product Version

4.0.14

Summary

0004377: CurlResource socket timeouts should pull initial values from JVM system properties

Description

By default, CurlResource is using infinite timeouts for socket connect and read timeouts. This is a severe problem for any hosted environment since threads blocking forever result eventually in a failure of the hosting environment. CurlResource should use non-infinite timeouts or provide a way to specify a non-infinite timeout value.

Additional Information

Another option is to check for the system properties sun.net.client.defaultConnectTimeout and sun.net.client.defaultReadTimeout as per http://download.oracle.com/javase/1.4.2/docs/guide/net/properties.html [^]

Attached Files

Relationships

Notes
(0005942) nam 06-23-12 11:28	If the user does not specify a timeout via setopt(), then curl will not set the Java timeout. This implies that the connection will use the default timeout, whatever that may be.

Issue History
Date Modified	Username	Field	Change
02-07-11 09:01	xerafin	New Issue
06-23-12 11:27	nam	Status	new => assigned
06-23-12 11:27	nam	Assigned To	=> nam
06-23-12 11:28	nam	Status	assigned => closed
06-23-12 11:28	nam	Note Added: 0005942
06-23-12 11:28	nam	Resolution	open => no change required

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.