[jira] [Commented] (NIFI-4988) UnpackContent throws "java.lang.IllegalArgumentException: invalid entry size" and Administratively Yields

2018-03-21 Thread William Vilwock (JIRA)

[ 
https://issues.apache.org/jira/browse/NIFI-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408256#comment-16408256
 ] 

William Vilwock commented on NIFI-4988:
---

Unfortunately, I cannot provide the data sample that caused this. Does the 
stack trace give you enough to go off of? 

> UnpackContent throws "java.lang.IllegalArgumentException: invalid entry size" 
> and Administratively Yields
> -
>
> Key: NIFI-4988
> URL: https://issues.apache.org/jira/browse/NIFI-4988
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.4.0, 1.5.0
>Reporter: William Vilwock
>Priority: Major
>
> When using the UnpackContent processor we sometimes receive the error 
> "java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
> file being routed to the failure relationship, the session is rolled back, 
> the flow file is penalized, and the framework "Administratively Yields". This 
> is causing our flow to back up. We would expect the malformed zip to be 
> routed to the failure relationship, not tried again. We received this 
> exception in both NiFi 1.4.0 and 1.5.0. 
> This is our exception stack trace:
> java.lang.IllegalArgumentException: invalid entry size
>  at 
> org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
>  at 
> org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
>  at 
> org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
>  at 
> org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
>  at 
> org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
>  at 
> org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
>  at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
>  at 
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
>  at 
> org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
>  at 
> org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
>  at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
>  at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
>  at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)
>  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>  at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (NIFI-4988) UnpackContent throws "java.lang.IllegalArgumentException: invalid entry size" and Administratively Yields

2018-03-16 Thread William Vilwock (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William Vilwock updated NIFI-4988:
--
Description: 
When using the UnpackContent processor we sometimes receive the error 
"java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
file being routed to the failure relationship, the session is rolled back, the 
flow file is penalized, and the framework "Administratively Yields". This is 
causing our flow to back up. We would expect the malformed zip to be routed to 
the failure relationship, not tried again. We received this exception in both 
NiFi 1.4.0 and 1.5.0. 

This is our exception stack trace:

java.lang.IllegalArgumentException: invalid entry size
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
 at 
org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
 at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

  was:
When using the UnpackContent processor we sometimes receive the error 
"java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
file being routed to the failure relationship, the session is rolled back, the 
flow file is penalized, and the framework "Administratively Yields". This is 
causing our flow to back up. We would expect the malformed zip to be routed to 
the failure relationship. not tried again. We received this exception in both 
NiFi 1.4.0 and 1.5.0. 

This is our exception stack trace:

java.lang.IllegalArgumentException: invalid entry size
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
 at 
org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
 at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
 at 

[jira] [Updated] (NIFI-4988) UnpackContent throws "java.lang.IllegalArgumentException: invalid entry size" and Administratively Yields

2018-03-16 Thread William Vilwock (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

William Vilwock updated NIFI-4988:
--
Description: 
When using the UnpackContent processor we sometimes receive the error 
"java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
file being routed to the failure relationship, the session is rolled back, the 
flow file is penalized, and the framework "Administratively Yields". This is 
causing our flow to back up. We would expect the malformed zip to be routed to 
the failure relationship. not tried again. We received this exception in both 
NiFi 1.4.0 and 1.5.0. 

This is our exception stack trace:

java.lang.IllegalArgumentException: invalid entry size
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
 at 
org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
 at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

  was:
When using the UnpackContent processor we sometimes receive the error 
"java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
file being routed to the error relationship, the session is rolled back, the 
flow file is penalized, and the framework "Administratively Yields". This is 
causing our flow to back up. We would expect the malformed zip to be routed to 
the failure relationship. not tried again. We received this exception in both 
NiFi 1.4.0 and 1.5.0. 

This is our exception stack trace:

java.lang.IllegalArgumentException: invalid entry size
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
 at 
org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
 at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
 at 

[jira] [Created] (NIFI-4988) UnpackContent throws "java.lang.IllegalArgumentException: invalid entry size" and Administratively Yields

2018-03-16 Thread William Vilwock (JIRA)
William Vilwock created NIFI-4988:
-

 Summary: UnpackContent throws "java.lang.IllegalArgumentException: 
invalid entry size" and Administratively Yields
 Key: NIFI-4988
 URL: https://issues.apache.org/jira/browse/NIFI-4988
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.5.0, 1.4.0
Reporter: William Vilwock


When using the UnpackContent processor we sometimes receive the error 
"java.lang.IllegalArgumentException: invalid entry size". Instead of the flow 
file being routed to the error relationship, the session is rolled back, the 
flow file is penalized, and the framework "Administratively Yields". This is 
causing our flow to back up. We would expect the malformed zip to be routed to 
the failure relationship. not tried again. We received this exception in both 
NiFi 1.4.0 and 1.5.0. 

This is our exception stack trace:

java.lang.IllegalArgumentException: invalid entry size
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveEntry.setSize(ZipArchiveEntry.java:679)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDataDescriptor(ZipArchiveInputStream.java:764)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.closeEntry(ZipArchiveInputStream.java:651)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextZipEntry(ZipArchiveInputStream.java:225)
 at 
org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.getNextEntry(ZipArchiveInputStream.java:378)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker$1.process(UnpackContent.java:362)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2175)
 at 
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:2145)
 at 
org.apache.nifi.processors.standard.UnpackContent$ZipUnpacker.unpack(UnpackContent.java:356)
 at 
org.apache.nifi.processors.standard.UnpackContent.onTrigger(UnpackContent.java:255)
 at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1122)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
 at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:128)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)