You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Shaun Longworth (JIRA)" <ji...@apache.org> on 2019/02/18 05:06:00 UTC

[jira] [Comment Edited] (NIFI-4970) EOF Exception in InvokeHttp when body's response is empty

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

Shaun Longworth edited comment on NIFI-4970 at 2/18/19 5:05 AM:
----------------------------------------------------------------

I have been troubleshooting this recently.  The existing code is checking if the variable responseBody is not null.  responseBody is an object and based on the definition of the property, it will never be null based on how it is used in the program.

Assuming the bodyExists variable gets set accordingly, the remaining portion of the code appears to work as expected.

 


was (Author: s_longworth):
I have been troubleshooting this recently.  The existing code is checking if the variable responseBody is not null.  responseBody is an object and based on the definition of the property, it will never be null based on how it is used in the program.  To rectify this, I suggest the following update:

 
{code:java}
// Nifi\nifi-nar-bundles\nifi-standard-bundle\nifi-standard-processors\src\main\java\org\apache\nifi\processors\standard\InvokeHTTP.java
// Line #824 (v1.8.0)

// Original code
boolean bodyExists = responseBody != null; 

// Suggested update
boolean bodyExists = (responseBody != null ? (responseBody.contentLength() > 0) : false);
{code}
 

This will ensure that the object is not null and if not null, check the length of the body.  If it is not found it will return -1.

Assuming the bodyExists variable gets set accordingly, the remaining portion of the code appears to work as expected.

 

> EOF Exception in InvokeHttp when body's response is empty 
> ----------------------------------------------------------
>
>                 Key: NIFI-4970
>                 URL: https://issues.apache.org/jira/browse/NIFI-4970
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.5.0
>         Environment: Apache NiFi - Version 1.5.0.3.1.1.0-35
>            Reporter: Francois Brillon
>            Priority: Major
>
> *Description*
> A POST to an API that returns an empty body on success (status code 200) will generate an EOF Exception, causing the processor to always remain in error and routing all flow files to failures, even if the API call succeeded.
> An example of such API is the Streaming API of PowerBI: [https://docs.microsoft.com/en-us/power-bi/service-real-time-streaming]
> *Exception Stack Traces*
> When the +property "Put Response Body In Attribute" is not set+, the exception is as follows:
> {code:java}
> rocessor.exception.FlowFileAccessException: Unable to create ContentClaim due to java.io.EOFException: org.apache.nifi.pro
> cessor.exception.FlowFileAccessException: Failed to import data from buffer(okio.GzipSource@159311b9).inputStream() for St
> andardFlowFileRecord[uuid=05a89e7b-d500-4d48-b034-52c7324fa6e6,claim=,offset=0,name=rtm-vehicle-position-20180313-182039.p
> b,size=0] due to org.apache.nifi.processor.exception.FlowFileAccessException: Unable to create ContentClaim due to java.io
> .EOFException
> org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from buffer(okio.GzipSource@159311b9).i
> nputStream() for StandardFlowFileRecord[uuid=05a89e7b-d500-4d48-b034-52c7324fa6e6,claim=,offset=0,name=rtm-vehicle-positio
> n-20180313-182039.pb,size=0] due to org.apache.nifi.processor.exception.FlowFileAccessException: Unable to create ContentC
> laim due to java.io.EOFException
> at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2942)
> at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:817)
> 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)
> Caused by: org.apache.nifi.processor.exception.FlowFileAccessException: Unable to create ContentClaim due to java.io.EOFException
> at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2935)
> ... 13 common frames omitted
> Caused by: java.io.EOFException: null
> at okio.RealBufferedSource.require(RealBufferedSource.java:59)
> at okio.GzipSource.consumeHeader(GzipSource.java:114)
> at okio.GzipSource.read(GzipSource.java:73)
> at okio.RealBufferedSource$1.read(RealBufferedSource.java:409)
> at java.io.InputStream.read(InputStream.java:101)
> at org.apache.nifi.stream.io.StreamUtils.copy(StreamUtils.java:35)
> at org.apache.nifi.controller.repository.FileSystemRepository.importFrom(FileSystemRepository.java:734)
> at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:2932)
> ... 13 common frames omitted
> {code}
> When +"Put Body Response in Attribute" property is set+, the exception is as follows :
> {code:java}
> 2018-03-13 18:32:13,165 ERROR [Timer-Driven Process Thread-3] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=5aae3a34-35d9-1268-6e6d-b774d4467e5a] Routing to Failure due to exception: java.io.EOFException: java.io.EOFException
> java.io.EOFException: null
>         at okio.RealBufferedSource.require(RealBufferedSource.java:59)
>         at okio.GzipSource.consumeHeader(GzipSource.java:114)
>         at okio.GzipSource.read(GzipSource.java:73)
>         at okio.RealBufferedSource$1.read(RealBufferedSource.java:409)
>         at org.apache.nifi.stream.io.StreamUtils.fillBuffer(StreamUtils.java:89)
>         at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:844)
>         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)
> {code}
>  
> *Possible Solution*
>  * Wrap calls to *fillBuffer* and *importFrom* into a try-catch
>  * Catch the EOF exception
>  * Generate an empty response (empty attribute or empty flow file) when this case occurs
> *Alternative Solution*
>  * Add a property indicating to the processor to ignore the body response
> *Additional Notes*
>  * There is currently an attempt to handle such case in the code, but it is not sufficient.
>  ** 
> {code:java}
>  boolean bodyExists = responseBody != null; {code}
>  * The variable bodyExists is true in the above case, even if no body has been returned by the REST API.



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