You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Joseph Percivall (JIRA)" <ji...@apache.org> on 2015/10/27 19:29:27 UTC

[jira] [Updated] (NIFI-883) HandleHttpRequest starts a web server in the OnScheduled method but should start it in onTrigger

     [ https://issues.apache.org/jira/browse/NIFI-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Percivall updated NIFI-883:
----------------------------------
    Attachment: NIFI-883_removed_lock.patch

[~markap14] You're right. I removed the lock and made it synchronized instead. I tested it using the template and it worked fine. I also rebased to master.

> HandleHttpRequest starts a web server in the OnScheduled method but should start it in onTrigger
> ------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-883
>                 URL: https://issues.apache.org/jira/browse/NIFI-883
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Joseph Percivall
>              Labels: beginner, newbie
>             Fix For: 0.4.0
>
>         Attachments: HttpRequestAndResponseTester.xml, NIFI-883.patch, NIFI-883_removed_lock.patch
>
>
> When HandleHttpRequest is scheduled, it creates an embedded jetty web server and starts it. Unfortunately, if this is run in a clustered environment and configured to run on Primary Node Only, all nodes still start the web server. This is very confusing if setting the Hostname property, as other nodes will complain.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)