Matt - No, I am not seeing this expected behavior. Nothing is being routed to "retry" as expected. IF I set "Always Output Response" = true the "Response" relationship is triggered and even in there you can see the "invoke.http.statuscode=502" I have attached a screenshot to show you what I mean. Looking at the code the only possible explanation for this would be that the incoming flowfile == null. Since my "InvokeHTTP" is a simple "GET" with no incoming flowfile I believe that the line at [1] is not being invoked as expected because the property at [2] is not set. However I do not want to set that property.
[1] https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java#L596 [2] https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java#L586 On Fri, Oct 14, 2016 at 12:11 PM, Matt Burgess <mattyb...@apache.org> wrote: > Jeremy, > > The code implies that 502 responses (actually all 5xx responses) are > routed to "retry" [1]. Are you not seeing that? > > Regards, > Matt > > [1] https://github.com/apache/nifi/blob/master/nifi-nar- > bundles/nifi-standard-bundle/nifi-standard-processors/src/ > main/java/org/apache/nifi/processors/standard/InvokeHTTP.java#L906 > > On Fri, Oct 14, 2016 at 11:59 AM, Jeremy Dyer <jdy...@gmail.com> wrote: > > I'm monitoring some micro services that sit behind an Nginx reverse > proxy. > > The idea is simple I want to fire off an alert if I get a "502 - Bad > > Gateway" response from Nginx which would mean that something has caused > the > > micro service to crash and then have NiFi attempt to restart the micro > > service. > > > > However no relationship is being invoked when a 502 response code is > > returned? Works great for 200 or even 500 but not getting any output what > > so ever for a 502? Any ideas? > > > > Thanks, > > Jeremy Dyer >
