|
Mantis - Quercus
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4377 | major | always | 02-07-11 09:01 | 06-23-12 11:28 | |
|
|
|||||
| Reporter: | xerafin | Platform: | |||
| Assigned To: | nam | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.14 | ||
| Product Build: | Resolution: | no change required | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | |||
|
|
|||||
| 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. |
||||
| Steps To Reproduce: | |||||
| 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 [^] | ||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||