[
https://issues.apache.org/jira/browse/NIFI-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188227#comment-15188227
]
Mark Payne commented on NIFI-1612:
----------------------------------
Found another spot within the site-to-site client where the timeout was not
utilized properly if not using secure communications.
In order to apply the patches, I expect the 0001* patch to be applied to
master, and then the 0002* patch applied on top of that.
To test, I found it easiest to create a VM and start nifi on the VM, with
site-to-site enabled. I also ran NiFi from local machine, with the patch
applied. I used site-to-site to push data to the VM. Then, when I confirmed
that the setup was working, I set the timeout on the Remote Process Group to 10
seconds instead of 30 seconds, verified all was still working, and then enabled
the firewall on my VM in order to cause the connections to timeout. I
continually tried to start & stop transmission on the Remote Process Group and
saw that the transmission was always disabled within that 10 second window.
> Remote Process Group is not using the configured Communications Timeout
> -----------------------------------------------------------------------
>
> Key: NIFI-1612
> URL: https://issues.apache.org/jira/browse/NIFI-1612
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.6.0
>
> Attachments:
> 0001-NIFI-1612-Do-not-ignore-Remote-Process-Group-s-timeo.patch,
> 0002-NIFI-1612-Found-a-spot-within-the-site-to-site-clien.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
