nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Payne <marka...@hotmail.com>
Subject Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0
Date Fri, 16 Nov 2018 20:13:34 GMT
Hi Jim,

Can you build a template of your flow and share that? If so, that's usually the easiest way
to try to
replicate the behavior and to understand exactly how your flow is configured.

Thanks
-Mark

On Nov 16, 2018, at 2:58 PM, Williams, Jim <jwilliams@alertlogic.com<mailto:jwilliams@alertlogic.com>>
wrote:

Hello,

I’m having an issue where the InvokeHTTP processor is apparently not producing a flow file,
and is also not throwing any errors.  This is occurring for a particular site, but I have
tested and found it to work for other sites.

Some observations:


  *   It was attempted to send all relationships to a PutFile processor, but no files were
generated
     *   The ‘Always Output Response’ setting was set to “true”, but still no files
were generated
  *   The processor is not generating any provenance events
  *   The bulletin level was set to DEBUG, but no bulletins were produced
  *   Debugging was added to the conf/logback.xml file after the ‘root’ entry, but no
debugging information was seen in logs/nifi-app.log :


    <root level="INFO">
        <appender-ref ref="APP_FILE"/>
    </root>

    <logger name="org.apache.nifi.processors.standard.InvokeHTTP" level="DEBUG" additivity="true">
        <appender-ref ref="APP_FILE"/>
    </logger>


Does someone have a suggestion of how we may get further information from this processor to
debug what we are seeing?


Warm regards,

<image001.jpg><https://www.alertlogic.com/>

Jim Williams | Principal Database Developer

O: +1 713.341.7812<tel:+1%20713.341.7812> | C: +1 919.523.8767<tel:+1%20919.523.8767>
| jwilliams@alertlogic.com<mailto:jwilliams@alertlogic.com> | alertlogic.com<http://www.alertlogic.com/>
<image002.png><https://twitter.com/alertlogic><image003.png><https://www.linkedin.com/company/alert-logic>



<image004.png>

Mime
View raw message