[jira] [Commented] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487796#comment-15487796
]
Vijay Panghal commented on JCLOUDS-1176:
One more observations -
When debug mode is enabled, we are not observing this IOException.
What I can understand from code, before this patch we were buffering the error
message in jclouds-core and then Openstack swift error handler used to read and
close the underlying connection. But after this patch jclouds-core is not
buffering the error response but Openstack swift error handler is trying to
read and close the connection and that causes this IOException.
This also explain how it is working in debug mode. As jcloud-core is buffering
the error message for logging purpose and openstack swift error handler is able
to read the error response and close the connection.
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at
[jira] [Commented] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487714#comment-15487714
]
Andrew Gaul commented on JCLOUDS-1176:
--
We should add a portable test for delete a non-existing object since all
providers should support this.
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at
[jira] [Comment Edited] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487796#comment-15487796
]
Vijay Panghal edited comment on JCLOUDS-1176 at 9/13/16 5:16 PM:
-
One more observation -
When debug mode is enabled, we are not observing this IOException.
What I can understand from code, before this patch we were buffering the error
message in jclouds-core and then Openstack swift error handler used to read and
close the underlying connection. But after this patch jclouds-core is not
buffering the error response but Openstack swift error handler is trying to
read and close the connection and that causes this IOException.
This also explain how it is working in debug mode. As jcloud-core is buffering
the error message for logging purpose and openstack swift error handler is able
to read the error response and close the connection.
was (Author: vpanghal):
One more observations -
When debug mode is enabled, we are not observing this IOException.
What I can understand from code, before this patch we were buffering the error
message in jclouds-core and then Openstack swift error handler used to read and
close the underlying connection. But after this patch jclouds-core is not
buffering the error response but Openstack swift error handler is trying to
read and close the connection and that causes this IOException.
This also explain how it is working in debug mode. As jcloud-core is buffering
the error message for logging purpose and openstack swift error handler is able
to read the error response and close the connection.
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> }
> +} catch (Exception e) {
> + logger.debug(e.toString());
> + // close pipe so client is notified of an exception
> + Closeables2.closeQuietly(input);
> + Closeables2.closeQuietly(output);
Would these work better in a `finally` block?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78608690
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> @@ -753,8 +770,24 @@ public Void call() {
> return null;
> }
> throw new RuntimeException("After " + retryCountLimit + " retries:
> " + lastException);
> + }
> +
> + // JDK-4715154
> + private void closeDirectBuffer(MappedByteBuffer mbb) {
> + if ( mbb == null || !mbb.isDirect() )
> +return;
> +
> + try {
> +Method cleaner = mbb.getClass().getMethod("cleaner");
Do we need to run this on all systems or just Windows?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78608199
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> @@ -753,8 +770,24 @@ public Void call() {
> return null;
> }
> throw new RuntimeException("After " + retryCountLimit + " retries:
> " + lastException);
> + }
> +
> + // JDK-4715154
> + private void closeDirectBuffer(MappedByteBuffer mbb) {
`static`?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78608102
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> @@ -706,12 +709,23 @@ public void downloadBlob(String container, String name,
> File destination, Execut
>
> Futures.getUnchecked(Futures.allAsList(results));
>
> + raf.getChannel().force(true);
> + raf.getChannel().close();
> + raf.close();
> +
> + if ( destination.exists() )
> +destination.delete();
> + if ( !tempFile.renameTo(destination) ) {
Please remove extra whitespace.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78608020
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> @@ -57,7 +57,7 @@
> public class RegionScopedSwiftBlobStoreParallelLiveTest extends
> BaseBlobStoreIntegrationTest {
>
> private final File BIG_FILE = new File("random.dat");
> - private final long SIZE = 10; //10 * 1000 * 1000;
> + private final long SIZE = 1000; //10 * 1000 * 1000;
Instead of the comment, could you just say:
```java
private static final long SIZE = 10 * 1000 * 1000;
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78608484
[jira] [Created] (JCLOUDS-1178) AWS vm deletion failed: did not retry on response "The service is unavailable. Please try again shortly"
navailable. Please try again
shortly.', context='{Response=, Errors=}'}
at
org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:75)
at
org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:136)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:105)
at
org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
at
org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117)
at
com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:87)
at com.sun.proxy.$Proxy160.describeInstancesInRegion(Unknown Source)
at
org.jclouds.ec2.compute.strategy.EC2GetNodeMetadataStrategy.getRunningInstanceInRegion(EC2GetNodeMetadataStrategy.java:64)
at
org.jclouds.aws.ec2.compute.strategy.AWSEC2GetNodeMetadataStrategy.getRunningInstanceInRegion(AWSEC2GetNodeMetadataStrategy.java:52)
at
org.jclouds.ec2.compute.strategy.EC2GetNodeMetadataStrategy.getNode(EC2GetNodeMetadataStrategy.java:56)
at
org.jclouds.compute.predicates.AtomicNodeTerminated.refreshOrNull(AtomicNodeTerminated.java:42)
at
org.jclouds.compute.predicates.AtomicNodeTerminated.refreshOrNull(AtomicNodeTerminated.java:28)
at
org.jclouds.compute.predicates.internal.TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse.apply(TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse.java:46)
at
org.jclouds.compute.predicates.internal.TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse.apply(TrueIfNullOrDeletedRefreshAndDoubleCheckOnFalse.java:31)
at
org.jclouds.util.Predicates2$RetryablePredicate.apply(Predicates2.java:117)
at
org.jclouds.compute.internal.BaseComputeService.doDestroyNode(BaseComputeService.java:302)
at
org.jclouds.compute.internal.BaseComputeService.destroyNode(BaseComputeService.java:243)
at
org.apache.brooklyn.location.jclouds.JcloudsLocation.releaseNode(JcloudsLocation.java:2701)
at
org.apache.brooklyn.location.jclouds.JcloudsLocation.release(JcloudsLocation.java:2651)
at
org.apache.brooklyn.entity.software.base.lifecycle.MachineLifecycleEffectorTasks.stopAnyProvisionedMachines(MachineLifecycleEffectorTasks.java:1021)
at
org.apache.brooklyn.entity.software.base.lifecycle.MachineLifecycleEffectorTasks$StopAnyProvisionedMachinesTask.call(MachineLifecycleEffectorTasks.java:875)
at
org.apache.brooklyn.entity.software.base.lifecycle.MachineLifecycleEffectorTasks$StopAnyProvisionedMachinesTask.call(MachineLifecycleEffectorTasks.java:873)
... 6 more
{noformat}
Digging into the jclouds wire log, I see:
{noformat}
2016-09-13 21:00:09,811 DEBUG o.j.r.i.InvokeHttpMethod
[brooklyn-execmanager-YxAEEeJK-3722]: >> invoking DescribeInstances
2016-09-13 21:00:09,812 DEBUG o.j.h.i.JavaUrlHttpCommandExecutorService
[brooklyn-execmanager-YxAEEeJK-3722]: Sending request -1247513718: POST
https://ec2.us-east-1.amazonaws.com/ HTTP/1.1
2016-09-13 21:00:09,812 DEBUG jclouds.wire
[brooklyn-execmanager-YxAEEeJK-3722]: >>
"Action=DescribeInstances=i-331bcea0=2012-06-01"
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> POST
https://ec2.us-east-1.amazonaws.com/ HTTP/1.1
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> Host: ec2.us-east-1.amazonaws.com
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> X-Amz-Date: 20160913T29Z
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> Authorization: AWS4-HMAC-SHA256
Credential=/20160913/us-east-1/ec2/aws4_request,
SignedHeaders=content-type;host;x-amz-date,
Signature=84cf762b171d56299b096a106733e72bbf96d5654b4c607135cea8cd7be51689
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> Content-Type:
application/x-www-form-urlencoded
2016-09-13 21:00:09,812 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: >> Content-Length: 67
2016-09-13 21:00:10,294 DEBUG o.j.h.i.JavaUrlHttpCommandExecutorService
[brooklyn-execmanager-YxAEEeJK-3722]: Receiving response -1247513718: HTTP/1.1
503 Service Unavailable
2016-09-13 21:00:10,294 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: << HTTP/1.1 503 Service Unavailable
2016-09-13 21:00:10,294 DEBUG jclouds.headers
[brooklyn-execmanager-YxAEEeJK-3722]: << Date: Tue, 13 Sep 2016 20:00:10 GMT
20
Re: [jclouds/jclouds] JCLOUDS-1161: Make AWSS3BlobRequestSignerV4 the default signer. (#1008)
Do the live tests run successfully on current master? The same 4 tests above failed for me on current master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1008#issuecomment-246837745
Re: [jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
> @@ -753,8 +770,24 @@ public Void call() {
> return null;
> }
> throw new RuntimeException("After " + retryCountLimit + " retries:
> " + lastException);
> + }
> +
> + // JDK-4715154
> + private void closeDirectBuffer(MappedByteBuffer mbb) {
> + if ( mbb == null || !mbb.isDirect() )
> +return;
> +
> + try {
> +Method cleaner = mbb.getClass().getMethod("cleaner");
Pretty sure only Windows. Could add an OS check.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1010/files/304c72c3e24e376cebbb98bd3b8f8ad6ecd72dac#r78688977
[jclouds/jclouds] More fixes to parallel download resource cleanup (#1010)
You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/1010 -- Commit Summary -- * More fixes to parallel download resource cleanup -- File Changes -- M apis/openstack-swift/src/main/java/org/jclouds/openstack/swift/v1/blobstore/RegionScopedSwiftBlobStore.java (59) M apis/openstack-swift/src/test/java/org/jclouds/openstack/swift/v1/blobstore/RegionScopedSwiftBlobStoreParallelLiveTest.java (3) -- Patch Links -- https://github.com/jclouds/jclouds/pull/1010.patch https://github.com/jclouds/jclouds/pull/1010.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1010
Re: [jclouds/jclouds] Some handles were not properly closed (#1007)
> @@ -701,14 +702,11 @@ public void downloadBlob(String container, String name,
> File destination, Execut
> Futures.getUnchecked(Futures.allAsList(results));
>
>} catch (IOException e) {
> - // cleanup, attempt to delete large file
> - if (raf != null) {
> -try {
> - raf.close();
> -} catch (IOException e1) {}
> - }
> + Closeables2.closeQuietly(raf);
https://github.com/jclouds/jclouds/pull/1010
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/1007/files/0003721c3e983e3f3c08824d86cbc7e5098f4eb4#r78502635
[jira] [Commented] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486872#comment-15486872
]
Zack Shoylev commented on JCLOUDS-1176:
---
I'll have a look.
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
[jclouds/jclouds-labs] fix azure-arm features live tests (#317)
When running in isolation the *LiveTests are working fine, they fail when running all together from maven. (see https://gist.github.com/andreaturli/2725723193ee1a8362f175e8e8c76ee8) You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds-labs/pull/317 -- Commit Summary -- * fix azure-arm features live tests -- File Changes -- M azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/DeploymentApi.java (20) M azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/util/DeploymentTemplateBuilder.java (3) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/DeploymentApiLiveTest.java (72) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/LocationApiLiveTest.java (4) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/NetworkInterfaceCardApiLiveTest.java (81) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/NetworkSecurityGroupApiLiveTest.java (93) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/NetworkSecurityRuleApiLiveTest.java (129) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/PublicIPAddressApiLiveTest.java (40) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/ResourceGroupApiLiveTest.java (64) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/StorageAccountApiLiveTest.java (48) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/SubnetApiLiveTest.java (63) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/TemplateToDeploymentTemplateLiveTest.java (36) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualMachineApiLiveTest.java (190) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/features/VirtualNetworkApiLiveTest.java (66) M azurecompute-arm/src/test/java/org/jclouds/azurecompute/arm/internal/BaseAzureComputeApiLiveTest.java (124) A azurecompute-arm/src/test/resources/logback-test.xml (34) D azurecompute-arm/src/test/resources/logback.xml (82) -- Patch Links -- https://github.com/jclouds/jclouds-labs/pull/317.patch https://github.com/jclouds/jclouds-labs/pull/317.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/317
[jira] [Commented] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486709#comment-15486709
]
Ignasi Barrera commented on JCLOUDS-1176:
-
[~zack-s] can you have a look at this? /cc [~gaul]
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
[jira] [Updated] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-1176:
Assignee: Zack Shoylev
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
>Assignee: Zack Shoylev
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
[jira] [Updated] (JCLOUDS-1176) Swift delete operation is not idempotent
[
https://issues.apache.org/jira/browse/JCLOUDS-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-1176:
Labels: openstack-swift (was: )
> Swift delete operation is not idempotent
>
>
> Key: JCLOUDS-1176
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1176
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
>Affects Versions: 1.9.0, 1.9.1, 1.9.2
>Reporter: Vijay Panghal
> Labels: openstack-swift
>
> Openstack Swift delete operation used to be idempotent. But after this pull
> request https://github.com/jclouds/jclouds/pull/700
> second delete is failing with these stack trace
> {quote}
> org.jclouds.http.HttpResponseException: java.io.IOException: stream is closed
> connecting to DELETE
> https://dal05.objectstorage.softlayer.net/v1/AUTH_0eb7ef10-6761-4384-ab47-9187592f30b1/cloud-testing/74f346838a7b550f
> HTTP/1.1
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:114)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:156)
> at
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:123)
> at com.sun.proxy.$Proxy67.removeObject(Unknown Source)
> at
> org.jclouds.openstack.swift.blobstore.SwiftBlobStore.removeBlob(SwiftBlobStore.java:260)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
> at com.sun.proxy.$Proxy69.removeBlob(Unknown Source)
> at
> com.maginatics.raptor.data.BlobStoreTest.testBlobRemoveIdempotence(BlobStoreTest.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:352)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
[jira] [Commented] (JCLOUDS-1132) Amazon AWS - Create Volume - query params reported as unrecognized
[ https://issues.apache.org/jira/browse/JCLOUDS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486632#comment-15486632 ] Felix Otto commented on JCLOUDS-1132: - Hi [~tusa.mihai], one question from side. Where I can find the code from pull request or is it already in the 1.9.x release branch? https://github.com/jclouds/jclouds/blob/1.9.x/core/src/main/java/org/jclouds/http/internal/JavaUrlHttpCommandExecutorService.java#L195 > Amazon AWS - Create Volume - query params reported as unrecognized > -- > > Key: JCLOUDS-1132 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1132 > Project: jclouds > Issue Type: Bug > Components: jclouds-compute >Affects Versions: 1.9.0, 1.9.2 > Environment: Amazon AWS EC2 management console >Reporter: Tusa Mihail Cristian > > Let say that I want to create a Volume that is encrypted. So, I set the > encrypted on "true"... in request query params apear "=true". In > this case the error that I got is: > UnknownParameterThe parameter > Encrypted is not > recognizedc874434a-b00e-425d-baf4-18087441603a > > instead it should be: "=1" as it is shown in Amazon docs: > http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html > in Example/Sample request. The problems are also related with Volume Type. If > not specified than creates a standard volume but if anything specified (any > of valid Values: standard | io1 | gp2 | sc1 | st1 ) the same error with > unrecognized param is received. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
