Giovanni, You are correct; the flowfile should have new attributes (invokehttp.status.code, etc.) on failure. Can you put a LogAttribute processor before and after the InvokeHTTP processor and print all of the attributes of the flowfile, then copy them here? If you can also share the configuration of your InvokeHTTP processor, that will help us diagnose the issue. Thanks.
Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 25, 2017, at 7:44 AM, Giovanni Lanzani > <[email protected]> wrote: > > Hi all, > > I'm using InvokeHTTP to do a POST request to a server. I'm trying to simulate > the server accepting connection but NOT giving response within the limit I > set in NiFi. > > The processor fails with SocketTimeoutException and the FlowFile is rerouted > to the Failure relationship (up until this: all is good!). > > The issue is that the exception was not written in the attributes of the > FlowFile. No attributes are modified when the failure is occurring. By > reading the docs for the failure relationship, I was under the impression > that: > > "The original FlowFile [...] will have new attributes detailing the request". > > But I think that maybe that is not correct?! (I'm using NiFi 1.0.0) > > Thanks in advance for everybody that might chime in! Sorry in advance if this > was a super dump question like my last one. > > Cheers, > > Giovanni
signature.asc
Description: Message signed with OpenPGP using GPGMail
