Re: PutTCP connector not cleaning up dangling connections

Stopping the processor doesn't cleanup the tcp connection. It remains ESTABLISHED. There are 2 ways of getting out of it (none of them are ideal). - Restarting Nifi - Restarting the Moxa serial ports I've dumped the output in the following gist :

Re: PutTCP connector not cleaning up dangling connections

If you stop the processor manually does it clean them up? When the connections appear stuck can you please get a thread dump? bin/nifi.sh dump The results end up in bootstrap.log. Thanks Joe On Sep 17, 2017 2:22 PM, "ddewaele" wrote: > We are using NiFi PutTCP processors

Re: PutEmail with Multiple Attachements

Thanks for your reply Customer was ok with the Zip approach, otherwise I would have used the ExecuteProcess processor to run a custom script. Mika> On 09/15/2017 07:39 PM, Joe Witt wrote: Mika, Could it be ok for your case to use MergeContent to package data together in some archive

PutTCP connector not cleaning up dangling connections

We are using NiFi PutTCP processors to send messages to a number of Moxa onCell ip gateway devices. These Moxa devices are running on a cellular network with not always the most ideal connection. The Moxa only allows for a maximum of 2 simultaneous client connections. What we notice is that

Manual release of flows

Hi, I have a use case where flow files should be blocked before moving to the next step. A manual action is needed to release these flow files. This manual action will be an HTTP post that an admin will be sending to NiFi through a simple web UI. How can I implement this behavior? Can I use