[
https://issues.apache.org/jira/browse/STREAMS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216417#comment-14216417
]
ASF GitHub Bot commented on STREAMS-225:
----------------------------------------
Github user rbnks commented on a diff in the pull request:
https://github.com/apache/incubator-streams/pull/134#discussion_r20519649
--- Diff:
streams-runtimes/streams-runtime-local/src/main/java/org/apache/streams/local/builders/LocalStreamBuilder.java
---
@@ -276,6 +283,14 @@ protected void shutdown(Map<String, List<StreamsTask>>
streamsTasks) throws Inte
}
}
+ private void clearJMXBeans() {
+ try {
+
ComponentUtils.removeAllMBeansOfDomain("org.apache.streams.local");
--- End diff --
This might not work correctly. If two streams are running on the same JVM,
this will clear out both streams JMXbeans.
> 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
>
> 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)
