Mailing-List: contact commits-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Date: Wed, 1 Jun 2016 02:51:12 +0000 (UTC)
From: "Steve Blackmon (JIRA)" <jira@apache.org>
To: commits@streams.incubator.apache.org
Message-ID: <JIRA.12755954.1416267043000.345276.1464749472829@Atlassian.JIRA>
In-Reply-To: <JIRA.12755954.1416267043000@Atlassian.JIRA>
References: <JIRA.12755954.1416267043000@Atlassian.JIRA> <JIRA.12755954.1416267043885@arcas>
Subject: [jira] [Commented] (STREAMS-225) Streams need to remove any of
 their JMX beans on shutdown/cleanup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Jun 2016 02:51:25 -0000


    [ https://issues.apache.org/jira/browse/STREAMS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309133#comment-15309133 ] 

Steve Blackmon commented on STREAMS-225:
----------------------------------------

closing.

> Streams need to remove any of their JMX beans on shutdown/cleanup
> -----------------------------------------------------------------
>
>                 Key: STREAMS-225
>                 URL: https://issues.apache.org/jira/browse/STREAMS-225
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Robert Douglas
>             Fix For: 0.2
>
>
> As a Streams developer, I should be able to run multiple Streams in a serial fashion without issue. Currently, JMX beans (which are used for monitoring the Stream's activity) are not cleared when a Stream is shutdown. If a new Stream is started afterwards (without a JVM restart) then there is a collision in the naming of the JMX beans which causes an exception which shuts down the subsequent Stream. Need to build in functionality to clear all JMX beans on shutdown.


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