Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/192#issuecomment-177524368
Think I found an edge case - I believe I successfully aborted an upload,
i.e., I had an upload half done, stopped the processor, flushed the queue,
waited, then sent a different file through, which logged that it aborted the
upload. I sent the same file through a while later and it failed with the
following stack trace -
```
2016-01-31 10:24:27,334 ERROR [Timer-Driven Process Thread-8]
o.a.nifi.processors.aws.s3.PutS3Object
com.amazonaws.services.s3.model.AmazonS3Exception: The specified upload
does not exist. The upload ID may be invalid, or the upload may have been
aborted or completed. (Service: Amazon S3; Status Code: 404; Error Code:
NoSuchUpload; Request ID: 998A0D40DE65697F)
at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1219)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:803)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:505)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:317)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595)
~[aws-java-sdk-s3-1.10.32.jar:na]
at
com.amazonaws.services.s3.AmazonS3Client.doUploadPart(AmazonS3Client.java:2733)
~[aws-java-sdk-s3-1.10.32.jar:na]
at
com.amazonaws.services.s3.AmazonS3Client.uploadPart(AmazonS3Client.java:2718)
~[aws-java-sdk-s3-1.10.32.jar:na]
at
org.apache.nifi.processors.aws.s3.PutS3Object$1.process(PutS3Object.java:506)
~[nifi-aws-processors-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1806)
~[na:na]
at
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1777)
~[na:na]
at
org.apache.nifi.processors.aws.s3.PutS3Object.onTrigger(PutS3Object.java:316)
~[nifi-aws-processors-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
[nifi-api-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1139)
[nifi-framework-core-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:139)
[nifi-framework-core-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:49)
[nifi-framework-core-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119)
[nifi-framework-core-0.4.2-SNAPSHOT.jar:0.4.2-SNAPSHOT]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[na:1.7.0_10]
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
[na:1.7.0_10]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
[na:1.7.0_10]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
[na:1.7.0_10]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.7.0_10]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[na:1.7.0_10]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[na:1.7.0_10]
at java.lang.Thread.run(Thread.java:722) [na:1.7.0_10]
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
