Worth looking at the sender's settings as well maybe - are they closing the connection prematurely (for example, some kind of timeout)?
*Chris Sampson* IT Consultant chris.samp...@naimuri.com On Fri, 7 Aug 2020 at 10:50, Pierre Villard <pierre.villard...@gmail.com> wrote: > Can you share the full stack trace? Anything specific between your client > and the ListenHTTP? Load balancer? > > I just did some tests and I could upload a 5GB file with no issue. I even > tried with the throttling parameters so that the upload takes a very long > time and it was fine as well. > > Le jeu. 6 août 2020 à 18:21, Michael Di Domenico <mdidomeni...@gmail.com> > a écrit : > >> On Thu, Aug 6, 2020 at 12:15 PM Joe Witt <joe.w...@gmail.com> wrote: >> > >> > ...I am confident far larger objects are sent via this mechanism >> reliably. Can you share what happens on the nifi side specifically? There >> should be a stack trace and log entry for this in the logs. >> > What are the settings you have in NiFi for this processor? How much >> storage space does your content repository have access to? >> >> I have no doubt. something is odd i just can't figure it out. There >> absolutely is a stack trace, but it's not easy for me to post. >> >> on my nifi side, i see the file start to down, up until it hits >> between 400-500MB, and then it stops and restarts. i'll retype some >> of the trace >> >> ERROR o.a.nifi.processors.standard.ListenHTTP Unable to receive file >> from Remote Host >> org.apache.nifi.process.exception.Process Exception: IOException >> thrown from ListenHTTP java.nio.channels.ClosedChannelException >> ...then a bunch of java routine errors... >> Suppressed: java.lang.Throwable: HttpInput failure >> >> there's plenty of storage, i only found this because nifi filled the >> partition with incomplete files. >> >> which settings do you want from listenhttp? >> >
