You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2012/05/29 06:27:23 UTC

[dev] [jira] [Resolved] (LIBCLOUD-199) Add http connection timeout to openstack and libcloud connections

     [ https://issues.apache.org/jira/browse/LIBCLOUD-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Muraus resolved LIBCLOUD-199.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.9.1)
                       (was: 0.8.0)
         Assignee: Tomaz Muraus

Merged into trunk, thanks.
                
> Add http connection timeout to openstack and libcloud connections
> -----------------------------------------------------------------
>
>                 Key: LIBCLOUD-199
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-199
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute, Core
>    Affects Versions: 0.8.0, 0.9.1
>            Reporter: Chris Gilmer
>            Assignee: Tomaz Muraus
>              Labels: auth, authentication, openstack,, timeout,
>         Attachments: openstack_and_libcloud_connection_timeout_patch.txt, openstack_and_libcloud_connection_timeout_patch_v2.txt, openstack_and_libcloud_connection_timeout_patch_v3.txt, openstack_and_libcloud_connection_timeout_patch_v4.txt, openstack_and_libcloud_connection_timeout_patch_v5.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Authentication calls to an openstack endpoint (in this case Rackspace) will occasionally create a connection that will stay open indefinitely.  By adding a timeout I can force the connection to close after a few seconds.  That way I can catch this behavior with an exception and log the error before the server request times out.  In this branch I add a timeout kwarg and set a reasonable default of 200 seconds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira