RE: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

2018-11-16 Thread Williams, Jim 
Mark,

 

Thanks for the observation and the hint!  I’ll change the flow and see if I get 
a better result.

 

 

Warm regards,

 


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

Jim Williams | Principal Database Developer


O: +1 713.341.7812 | C: +1 919.523.8767 | jwilli...@alertlogic.com |  
<http://www.alertlogic.com/> alertlogic.com  <https://twitter.com/alertlogic>  
<https://www.linkedin.com/company/alert-logic> 


 



 

From: Mark Payne  
Sent: Friday, November 16, 2018 3:14 PM
To: users@nifi.apache.org
Subject: Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

 

Jim, 

 

Thanks, that's enough to understand what's happening. As it is configured, the 
InvokeHTTP processor has no incoming connection.

However, it is configured to use the HTTP POST method. It doesn't really make 
sense to perform a POST with no incoming data,

so the Processor just returns. If you have no incoming connection, you cannot 
use the Processor to perform a POST, PUT, or PATCH

request.

 

You could force it to occur, if you want to, because the service does something 
interesting with an empty POST, by using a GenerateFlowFile

processor ahead of it and generating a 0-byte FlowFile, then sending that to 
the InvokeHTTP processor.

 

Thanks

-Mark

 

 





On Nov 16, 2018, at 3:29 PM, Williams, Jim mailto:jwilli...@alertlogic.com> > wrote:

 

Hey Mark,

 

Replication is problematic, since the HTTP server I am accessing is internal to 
my company.  However, I have attached a template of the (rather simple) flow.

 

 

Warm regards,

 


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

Jim Williams | Principal Database Developer


O:   +1 713.341.7812 | C:   +1 
919.523.8767 |  <mailto:jwilli...@alertlogic.com> jwilli...@alertlogic.com |  
<http://www.alertlogic.com/> alertlogic.com  
<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_alertlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=13mmQmOyilSae-MGpp3n8sGR_dlBGlPONs657tD53KM=DZ3ro4bxRxFa1X8Ch7qXHm0cqWDW9EPY0EXGobLGdjs=>
  
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_alert-2Dlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=13mmQmOyilSae-MGpp3n8sGR_dlBGlPONs657tD53KM=hv3BdhKofz8u169QQKemxYQlZVQTaIPpldPYlUDfu5s=>
 


 



 

From: Mark Payne mailto:marka...@hotmail.com> > 
Sent: Friday, November 16, 2018 2:14 PM
To: users@nifi.apache.org <mailto:users@nifi.apache.org> 
Subject: Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

 

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 < <mailto:jwilli...@alertlogic.com> 
jwilli...@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 :

 







 







 

 

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

 

 

Warm regards,

 


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

Jim Williams | Principal Database Developer


O:   +1 713.341.7812 | C:   +1 
919.523.8767 |  <mailto:jwilli...@alertlogic.com> jwilli...@alertlogic.com |  
<http://www.alertlogic.com/> alertlogic.com  
<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_alertlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=x-wAa94k2BSEEhmcwCQMcnSH5gNlbTF7hxnLddLupv0=OQhUqh_o2_0BmYfe_Mv5D6pRAFa42n8rJObmUpZSGuE=>
  
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_alert-2Dlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=x-wAa94k2BSEEhmcwCQMcnSH5gNlbTF7hxnLddLupv0=k1rniGCDMSDCanKifFM6Heh4PJSWHAu9MhnOKdaST5Y=>
 


 



 



 



smime.p7s
Description: S/MIME cryptographic signature

Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

2018-11-16 Thread Mark Payne 
Jim,

Thanks, that's enough to understand what's happening. As it is configured, the 
InvokeHTTP processor has no incoming connection.
However, it is configured to use the HTTP POST method. It doesn't really make 
sense to perform a POST with no incoming data,
so the Processor just returns. If you have no incoming connection, you cannot 
use the Processor to perform a POST, PUT, or PATCH
request.

You could force it to occur, if you want to, because the service does something 
interesting with an empty POST, by using a GenerateFlowFile
processor ahead of it and generating a 0-byte FlowFile, then sending that to 
the InvokeHTTP processor.

Thanks
-Mark



On Nov 16, 2018, at 3:29 PM, Williams, Jim 
mailto:jwilli...@alertlogic.com>> wrote:

Hey Mark,

Replication is problematic, since the HTTP server I am accessing is internal to 
my company.  However, I have attached a template of the (rather simple) flow.


Warm regards,

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

Jim Williams | Principal Database Developer

O: +1 713.341.7812 | C: +1 
919.523.8767 | 
jwilli...@alertlogic.com<mailto:jwilli...@alertlogic.com> | 
alertlogic.com<http://www.alertlogic.com/> 
<https://twitter.com/alertlogic><https://www.linkedin.com/company/alert-logic>





From: Mark Payne mailto:marka...@hotmail.com>>
Sent: Friday, November 16, 2018 2:14 PM
To: users@nifi.apache.org<mailto:users@nifi.apache.org>
Subject: Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

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 
mailto:jwilli...@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 :











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


Warm regards,

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

Jim Williams | Principal Database Developer

O: +1 713.341.7812 | C: +1 
919.523.8767 | 
jwilli...@alertlogic.com<mailto:jwilli...@alertlogic.com> | 
alertlogic.com<http://www.alertlogic.com/> 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_alertlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=x-wAa94k2BSEEhmcwCQMcnSH5gNlbTF7hxnLddLupv0=OQhUqh_o2_0BmYfe_Mv5D6pRAFa42n8rJObmUpZSGuE=><https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_alert-2Dlogic=DwMGaQ=L_h2OePR2UWWefmqrezxOsP9Uqw55rRfX5bRtw9S4KY=8BKCOHGXeuGDgPbW9jE4jktuFFiof_whsQaGaYqyyjs=x-wAa94k2BSEEhmcwCQMcnSH5gNlbTF7hxnLddLupv0=k1rniGCDMSDCanKifFM6Heh4PJSWHAu9MhnOKdaST5Y=>

Re: Problem Debugging InvokeHTTP Processor in Nifi 1.8.0

2018-11-16 Thread Mark Payne 
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 
mailto:jwilli...@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 :











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


Warm regards,



Jim Williams | Principal Database Developer

O: +1 713.341.7812 | C: +1 
919.523.8767 | 
jwilli...@alertlogic.com | 
alertlogic.com