Return-Path: X-Original-To: apmail-nifi-commits-archive@minotaur.apache.org Delivered-To: apmail-nifi-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C64B618E8E for ; Wed, 24 Jun 2015 00:17:44 +0000 (UTC) Received: (qmail 12193 invoked by uid 500); 24 Jun 2015 00:17:44 -0000 Delivered-To: apmail-nifi-commits-archive@nifi.apache.org Received: (qmail 12159 invoked by uid 500); 24 Jun 2015 00:17:44 -0000 Mailing-List: contact commits-help@nifi.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.incubator.apache.org Delivered-To: mailing list commits@nifi.incubator.apache.org Received: (qmail 12150 invoked by uid 99); 24 Jun 2015 00:17:44 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2015 00:17:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4CCD3CFC61 for ; Wed, 24 Jun 2015 00:17:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.352 X-Spam-Level: X-Spam-Status: No, score=0.352 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.428] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id alx9N25O1l6H for ; Wed, 24 Jun 2015 00:17:43 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id B658024A5E for ; Wed, 24 Jun 2015 00:17:43 +0000 (UTC) Received: (qmail 12060 invoked by uid 99); 24 Jun 2015 00:17:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2015 00:17:43 +0000 Date: Wed, 24 Jun 2015 00:17:43 +0000 (UTC) From: "Mark Payne (JIRA)" To: commits@nifi.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598625#comment-14598625 ] Mark Payne commented on NIFI-720: --------------------------------- [~mcgilman] sorry, cleaned up some code and lost my 'return' statement. Attached a new patch that will hopefully work better for you :) > If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start > -------------------------------------------------------------------------------------------------------------- > > Key: NIFI-720 > URL: https://issues.apache.org/jira/browse/NIFI-720 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Reporter: Mark Payne > Assignee: Mark Payne > Fix For: 0.2.0 > > Attachments: 0001-NIFI-720-Ensure-that-if-Reporting-Task-stopped-while.patch > > > Steps to replicate: > Create a MonitorMemory reporting task. > Set an invalid value for the Memory Pool > Start the reporting task > See that errors are logged indicating that it couldn't start properly > Stop Reporting Task > Change Memory Pool to a valid value > MonitorMemory will begin to run. Clicking Start will cause two threads to now run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)