You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/06/19 20:12:20 UTC

[jira] [Commented] (JCLOUDS-137) Atmos should retry on HTTP 500 AtmosError 1040

    [ https://issues.apache.org/jira/browse/JCLOUDS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688241#comment-13688241 ] 

Andrew Bayer commented on JCLOUDS-137:
--------------------------------------

Hey, sounds like JCLOUDS-100! =)
                
> Atmos should retry on HTTP 500 AtmosError 1040
> ----------------------------------------------
>
>                 Key: JCLOUDS-137
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-137
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.0, 1.6.1
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>
> I experience many of these errors while clearing a large Atmos container:
> org.jclouds.atmos.AtmosResponseException: command DELETE https://api.atmosonline.com/rest/namespace/gaultest/00/00/03/37ab304c488645c7400f0e2aea272a74-7719 HTTP/1.1 failed with code 500, error: AtmosError [code=1040, message=The server is busy. Please try again.]
> Looking at AtmosRestClientModule we do not bind a retry handle for server errors as we do for client errors with AtmosClientErrorRetryHandler.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira