nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <>
Subject Re: NiFi ListenTCP 1.4.0 "Rejecting Connections from xx.xx.xx.xx : xxxx, because max connection has been met" timeout
Date Mon, 21 May 2018 13:16:42 GMT
The max connection warning is simply based on the property in the
processor called "Max Number of TCP Connections" which defaults to 2.
So in the default case, if a third connection is made while two
connections are open, then the third connection is rejected and you
see this warning.

If you are saying that the issue eventually corrects it self, then
maybe just increase the max allowed connections slightly.

If that is not helping, are there any other errors in the NiFi logs
around the time of connection loss? (besides the rejected connections
that happen later).


On Mon, May 21, 2018 at 3:36 AM, yi <> wrote:
> Hi there,
> I am using a ListenTCP to capture data coming from an Arduino on a TCP port
> over WiFi.
> When there is a loss of comms over wifi for various reasons (loss of signal,
> power cut), the Arduino is programmed to attempt to connect back when
> connection is restored.
> I am seeing at times the max connections warning as the arduino attemps to
> reconnect, and it is unable to regain data flow for a long time - it seems
> to be a random amount of time from a few minutes up to half an hour.
> I have had a look at this article
> which suggests that the Arduino side should close the connection, however
> during an abrupt connection loss, NiFi would not be able to detect a
> closure.
> Does anybody know if there is a set timeout period on the max connections
> condition?
> Is there a way to control how the max connection warning is triggered?
> Thank you
> --
> Sent from:

View raw message