Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.6.1, 1.7.0
-
None
Description
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.