nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (NIFI-1690) Misconfigured MonitorMemory ReportingTask can not be stopped
Date Thu, 16 Jun 2016 23:11:05 GMT


ASF subversion and git services commented on NIFI-1690:

Commit 8e4a4532df92e6b1e0a461454a7440005a6bee7d in nifi's branch refs/heads/master from [~ozhurakousky]
[;h=8e4a453 ]

NIFI-1690 Changed MonitorMemory to use allowable values for pool names
- removed dead code from MonitorMemory
- added MonitorMemoryTest
- minor refactoring in MonitorMemory
- initial fix for NIFI-1731 (WARN/INFO logging) that was required by MonitorMemoryTest

NIFI-1690 polishing

NIFI-1690 address PR comments, removed default value for MEMORY_POOL_PROPERTY

NIFI-1690 addressed latest PR comments

NIFI-1690 fixed breaking changes

Fixed checkstyle issue in StandardProcessScheduler. (+2 squashed commits)
Squashed commits:
[03829c4] Fixed checkstyle issues.

This closes #328.

Signed-off-by: Andy LoPresto <>

> Misconfigured MonitorMemory ReportingTask can not be stopped
> ------------------------------------------------------------
>                 Key: NIFI-1690
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.5.1
>            Reporter: Matthew Clarke
>            Assignee: Oleg Zhurakousky
>             Fix For: 1.0.0, 0.7.0
>      The monitor memory reporting tasks allows the user to entire any value they want
for the JVM memory pool. If the supplied value is not valid (NiFi can not find a memory pool
with the supplied value), the reporting tasks appears to get stuck in the @onDemand state.
 At this point the task can not be stopped, edited, or deleted.

This message was sent by Atlassian JIRA

View raw message