Not related to Nifi, but I faced the same type of issue for endpoints behind a proxy which takes more than 30 seconds to answer. Fixed by replacing Apache Http client by OkHttp. I did not investigate further, just simply replaced one library by another and the error was fixed.
Juan On Sat, 29 May 2021 at 15:08, Robert R. Bruno <rbru...@gmail.com> wrote: > I wanted to see if anyone has any ideas on this one. Since upgrading to > 1.13.2 from 1.9.2 we are starting to see broken pipe (write failed) errors > from a few invokeHttp processers. > > It is happening to processors talking to different endpoints, so I am > suspecting it is on the nifi side. We are now using load balanced queues > throughout our flow. Is it possible we are hitting a http connection > resource issue or something like that? A total guess I'll admit. > > If this could be it, does anyone know which parameter(s) to play with in > the properties file? I know there is one setting for jetty threads and > another for max concurrent requests, but it isn't quite clear to me of they > are at all involved with invokeHttp calls. > > Thanks in advance! > > Robert >
