[jboss-jira] [JBoss JIRA] Commented: (JBREM-754) Reset timeout on each use of HttpURLConnection

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-754?page=comments#action_12364646 ] 
            
Ron Sigal commented on JBREM-754:
---------------------------------

HTTPClientInvoker now explicitly sets the timeout.  This applies in the case of jdk >= 1.5.

Unit test:  org.jboss.test.remoting.transport.http.timeout.ReusedHttpURLConnectionsTestCase.

> Reset timeout on each use of HttpURLConnection
> ----------------------------------------------
>
>                 Key: JBREM-754
>                 URL: http://jira.jboss.com/jira/browse/JBREM-754
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Even though each call to org.jboss.remoting.transport.http.HTTPClientInvoker.invoke() creates a new HttpURLConnection, it seems that the HttpURLConnection implementation caches underlying connections.  When an org.jboss.remoting.ConnectionValidator is running, it connects to the same server as ordinary HTTPClientInvokers used by the application, but it sets a timeout of 1000.  If no timeout value is configured for application connections, then HTTPClientInvoker does not set a timeout on the HttpURLConnection, and a connection with a timeout of 1000 might get reused.
> If no timeout is configured, HTTPClientInvoker should explicitly set the HttpURLConnection connect and read timeouts to 0.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira