[jira] [Commented] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
[
https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014064#comment-14014064
]
Bill Branan commented on JCLOUDS-498:
-
[~andrewp]: I did some testing with the SwiftApi in 1.7.2, but wasn't able to
get things working. The OpenStack provider I'm connecting to primarily (SDSC
Cloud) doesn't expose a keystone v2.0 auth endpoint yet (only v1.0). As far as
I could tell, the 405 Method Not Allowed errors I was seeing were due to
unsupported calls being made trying to get an auth token. I also tried
connecting to Rackspace, but ended up with 401 Unauthorized errors, at which
point I decided to cut my losses and move along.
PUT object calls fail against Swift with JClouds 1.7.1
--
Key: JCLOUDS-498
URL: https://issues.apache.org/jira/browse/JCLOUDS-498
Project: jclouds
Issue Type: Bug
Components: jclouds-blobstore
Affects Versions: 1.7.1
Environment: Tested on Windows 7 with Java 1.7.0_45
Reporter: Bill Branan
Priority: Critical
I am attempting to upgrade my application from JClouds 1.5.5 to JClouds
1.7.1. My application connects to an OpenStack Swift storage provider for
storing objects. After updating to 1.7.1 all calls seem to work except the
calls to store new objects. I've tested listing containers, updating object
properties, deleting objects, and deleting containers, and all of these work,
but putting a new object does not.
The error I see when attempting to put a new object is listed below. I get
this error regardless of whether I am using the SwiftClient or the BlobStore
interface.
I wrote up some tests to isolate the issue.
The test for 1.7.1 is here:
https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1
The test for 1.5.5 is here:
https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5
The tests can be built using ant and run using ant run. The tests work
perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple
params at the top of the Java class prior to building.)
I should also note that the tests for 1.7.1 pass when I connect to Rackspace,
but fail when I connect to SDSC Cloud, so there may be differences between
OpenStack Swift providers that are not being accounted for. SDSC Cloud is
running the Grizzly version of Swift.
The error I see on PUT failure:
{noformat}
[java] SEVERE: Cannot retry after server error, command is not
replayable: [method=public abstract
com.google.common.util.concurrent.ListenableFuture
org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java.lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389,
[info=[contentDisposition=null, contentEncoding=null, contentLanguage=null,
contentLength=null, contentMD5=null, contentType=application/unknown,
expires=null]]], request=PUT
https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119
HTTP/1.1]
[java] PUT failed with error: Read timed out connecting to PUT
https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119
HTTP/1.1
[java] org.jclouds.http.HttpResponseException: Read timed out connecting
to PUT
https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119
HTTP/1.1
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JCLOUDS-278) SwiftClient parse exception on '%' symbols
[
https://issues.apache.org/jira/browse/JCLOUDS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014192#comment-14014192
]
Bill Branan commented on JCLOUDS-278:
-
Updated pull request against master branch:
https://github.com/jclouds/jclouds/pull/388.
SwiftClient parse exception on '%' symbols
--
Key: JCLOUDS-278
URL: https://issues.apache.org/jira/browse/JCLOUDS-278
Project: jclouds
Issue Type: Bug
Affects Versions: 1.5.10, 1.6.2
Environment: Tested on:
org.jclouds:jclouds-allblobstore:1.5.5
AND
org.apache.jclouds:jclouds-allblobstore:1.6.2-incubating
Reporter: Erik Paulsson
I've tested this using org.jclouds:jclouds-allblobstore v1.5.5 and
1.6.2-incubating. I get a parse exception using the SwiftClient when object
names contain a '%' symbol.
For example an object whose name is 'AND_-_100%_TVX/test.txt' will get stored
fine, but when I attempt to list the contents of the container that the
object is in I get the following exception:
Sep 10, 2013 10:26:40 AM org.jclouds.logging.jdk.JDKLogger logError
SEVERE: Error parsing input
java.lang.IllegalArgumentException: URLDecoder: Illegal hex characters in
escape (%) pattern - For input string: _T
at java.net.URLDecoder.decode(URLDecoder.java:192)
at org.jclouds.util.Strings2.urlDecode(Strings2.java:97)
at org.jclouds.http.Uris$UriBuilder.appendPath(Uris.java:157)
at
org.jclouds.openstack.swift.functions.ParseObjectInfoListFromJsonResponse$3.apply(ParseObjectInfoListFromJsonResponse.java:82)
at
org.jclouds.openstack.swift.functions.ParseObjectInfoListFromJsonResponse$3.apply(ParseObjectInfoListFromJsonResponse.java:80)
at com.google.common.collect.Iterators$9.transform(Iterators.java:893)
at
com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48)
at com.google.common.collect.Sets.newTreeSet(Sets.java:345)
at
org.jclouds.openstack.swift.functions.ParseObjectInfoListFromJsonResponse.apply(ParseObjectInfoListFromJsonResponse.java:79)
at
org.jclouds.openstack.swift.functions.ParseObjectInfoListFromJsonResponse.apply(ParseObjectInfoListFromJsonResponse.java:54)
at org.jclouds.http.functions.ParseJson.apply(ParseJson.java:66)
at org.jclouds.http.functions.ParseJson.apply(ParseJson.java:46)
at com.google.common.util.concurrent.Futures$3.apply(Futures.java:376)
at
com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:518)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
This may affect more than just the SwiftClient API since it looks like the
bug may be in:
org.jclouds.util.Strings2.urlDecode
org.jclouds.http.Uris$UriBuilder.appendPath
Here is an example of a simple method that generates the exception:
private PageSetObjectInfo listObjects(String containerName,
String prefix,
int maxResults,
String marker) {
ListContainerOptions containerOptions =
ListContainerOptions.Builder.maxResults(maxResults);
if(marker != null) containerOptions.afterMarker(marker);
if(prefix != null) containerOptions.withPrefix(prefix);
return swiftClient.listObjects(containerName, containerOptions);
}
Calling this method with the container name of the container containing the
object whose name contains a '%' symbol and a maxResults of 1000 and null for
both prefix and marker will result in the above exception.
Let's just say my container name is percent-container and I have an object
in this container with the name AND_-_100%_TVX/test.txt
So this is what the method call to the above method might look like:
listObjects(percent-container, null, 1000, null);
Even if I URL encode the object name before storing it I still get the same
exception when retrieving a list of contents for the space.
I can run a cURL command straight to the Swift storage provider to get the
object and it returns fine.
Am I doing anything wrong? Do I need to handle '%' symbols in a special way?
The docs swift docs don't express any character restrictions on object
names:
http://docs.openstack.org/trunk/openstack-object-storage/admin/content/containers-and-objects.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
[ https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13940977#comment-13940977 ] Bill Branan commented on JCLOUDS-498: - From the SDSC Cloud folks on a discussion about this issue: Looking at our logs we are getting 499 and 408 errors when you use jclouds/1.7.1 but everything works fine when you use jclouds/1.5.5. 408 and 499 errors typically mean it is a client side error. They suggested that this may be related to JCLOUDS-342. The work done on that issue seems like a possible fix for the 408 errors, but wouldn't address the 499s. PUT object calls fail against Swift with JClouds 1.7.1 -- Key: JCLOUDS-498 URL: https://issues.apache.org/jira/browse/JCLOUDS-498 Project: jclouds Issue Type: Bug Components: jclouds-blobstore Affects Versions: 1.7.1 Environment: Tested on Windows 7 with Java 1.7.0_45 Reporter: Bill Branan Priority: Critical I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. SDSC Cloud is running the Grizzly version of Swift. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-b lob-1394647701119 HTTP/1.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
[ https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938488#comment-13938488 ] Bill Branan commented on JCLOUDS-498: - Hi Jeremy, I just tried a PUT call to store content in SDSC Cloud using curl, and it worked just fine. As I mentioned before, storing content in SDSC Cloud using JClouds 1.5.5 also works just fine. Any thoughts as to why I would get a timeout with the 1.7.1 client, but not with the 1.5.5 client? Was there an expected change in the way this call is handled between the versions? Thanks, Bill PUT object calls fail against Swift with JClouds 1.7.1 -- Key: JCLOUDS-498 URL: https://issues.apache.org/jira/browse/JCLOUDS-498 Project: jclouds Issue Type: Bug Components: jclouds-blobstore Affects Versions: 1.7.1 Environment: Tested on Windows 7 with Java 1.7.0_45 Reporter: Bill Branan Priority: Critical I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. SDSC Cloud is running the Grizzly version of Swift. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-b lob-1394647701119 HTTP/1.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
[ https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Branan updated JCLOUDS-498: Description: I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. SDSC Cloud is running the Grizzly version of Swift. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-b lob-1394647701119 HTTP/1.1 was: I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT
[jira] [Commented] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
[ https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934187#comment-13934187 ] Bill Branan commented on JCLOUDS-498: - Hi Jeremy, I've updated the 1.7.1 test code I linked in the description to now capture logs, based on your suggestion. Here is a gist with the full command line output, the jclouds.log output and the jclouds-wire.log output: https://gist.github.com/bbranan/9537885. Thanks for taking a look! Bill PUT object calls fail against Swift with JClouds 1.7.1 -- Key: JCLOUDS-498 URL: https://issues.apache.org/jira/browse/JCLOUDS-498 Project: jclouds Issue Type: Bug Components: jclouds-blobstore Affects Versions: 1.7.1 Environment: Tested on Windows 7 with Java 1.7.0_45 Reporter: Bill Branan Priority: Critical I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. SDSC Cloud is running the Grizzly version of Swift. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-b lob-1394647701119 HTTP/1.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (JCLOUDS-498) PUT object calls fail against Swift with JClouds 1.7.1
Bill Branan created JCLOUDS-498: --- Summary: PUT object calls fail against Swift with JClouds 1.7.1 Key: JCLOUDS-498 URL: https://issues.apache.org/jira/browse/JCLOUDS-498 Project: jclouds Issue Type: Bug Components: jclouds-blobstore Affects Versions: 1.7.1 Environment: Tested on Windows 7 with Java 1.7.0_45 Reporter: Bill Branan Priority: Critical I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1. My application connects to an OpenStack Swift storage provider for storing objects. After updating to 1.7.1 all calls seem to work except the calls to store new objects. I've tested listing containers, updating object properties, deleting objects, and deleting containers, and all of these work, but putting a new object does not. The error I see when attempting to put a new object is listed below. I get this error regardless of whether I am using the SwiftClient or the BlobStore interface. I wrote up some tests to isolate the issue. The test for 1.7.1 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.7.1 The test for 1.5.5 is here: https://github.com/bbranan/sdsc-tests/tree/master/sdsc-jclouds-1.5.5 The tests can be built using ant and run using ant run. The tests work perfectly with 1.5.5, but fail with 1.7.1. (You'll need to enter a couple params at the top of the Java class prior to building.) I should also note that the tests for 1.7.1 pass when I connect to Rackspace, but fail when I connect to SDSC Cloud, so there may be differences between OpenStack Swift providers that are not being accounted for. The error I see on PUT failure: [java] SEVERE: Cannot retry after server error, command is not replayable: [method=public abstract com.google.common.util.concurrent.ListenableFuture org.jclouds.openstack.swift.CommonSwiftAsyncClient.putObject(java .lang.String,org.jclouds.openstack.swift.domain.SwiftObject)[test-container-1394647640389, [info=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=appl ication/unknown, expires=null]]], request=PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-1394647701119 HTTP/1.1] [java] PUT failed with error: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-blob-13946477011 19 HTTP/1.1 [java] org.jclouds.http.HttpResponseException: Read timed out connecting to PUT https://duracloud.auth.cloud.sdsc.edu:443/v1/DURACLOUD_36ef189e-614e-49a9-bb8d-84f66e8553d5/test-container-1394647640389/test-content-b lob-1394647701119 HTTP/1.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
