Upgrade to DuraCloud API v2.1.3, which provides a backported connection bug fix related to the most recent release of DuraCloud. #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the release of DuraCloud 2.4.0, users of 'dspace-replicate' 1.x (with DSpace 1.8.x) have reported connection problems to DuraCloud.
These DuraCloud connection errors would look like:
java.io.IOException: Unable to connect to the DuraCloud Primary Content Store. Please check the DuraCloud connection/authentication settings in your 'duracloud.cfg' file.
...
Caused by: org.duracloud.error.ContentStoreException: Error retrieving content stores. null
This connection issue was a small issue in the older 2.1.x version of the DuraCloud API (around retrieving content stores, as the error implies) and it has now been resolved in DuraCloud API v2.1.3. Unfortunately, 'dspace-replicate' 1.x is limited to using the 2.1.x DuraCloud API, as it was the last version that supported Java 6.
I'll merge this fix shortly, as I've verified it resolves the connection issues with latest DuraCloud. I'll also release a new version of the Replication Task Suite which affected DSpace 1.8.x users can upgrade to.