You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/09/27 15:40:07 UTC
[jira] [Created] (CAMEL-5656) JMXConnector is started async, should
terminate thread after started to avoid keeping around
Claus Ibsen created CAMEL-5656:
----------------------------------
Summary: JMXConnector is started async, should terminate thread after started to avoid keeping around
Key: CAMEL-5656
URL: https://issues.apache.org/jira/browse/CAMEL-5656
Project: Camel
Issue Type: Improvement
Components: camel-core, jmx
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.9.4, 2.11.0, 2.10.2
When using JMX Connector then its started async using a single thread pool. This is not needed as the thread should be terminated after usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5656) JMXConnector is started async,
should terminate thread after started to avoid keeping around
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464726#comment-13464726 ]
Claus Ibsen commented on CAMEL-5656:
------------------------------------
2012-09-27 15:28:10,082 [main ] WARN DefaultExecutorServiceManager - Forcing shutdown of ExecutorService: org.apache.camel.util.concurrent.RejectableThreadPoolExecutor@54c8ab35[Running, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1][JMXConnector: service:jmx:rmi:///jndi/rmi://davsclaus.lan:1099/jmxrmi/camel]
> JMXConnector is started async, should terminate thread after started to avoid keeping around
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-5656
> URL: https://issues.apache.org/jira/browse/CAMEL-5656
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> When using JMX Connector then its started async using a single thread pool. This is not needed as the thread should be terminated after usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5656) JMXConnector is started async,
should terminate thread after started to avoid keeping around
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5656.
--------------------------------
Resolution: Fixed
> JMXConnector is started async, should terminate thread after started to avoid keeping around
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-5656
> URL: https://issues.apache.org/jira/browse/CAMEL-5656
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> When using JMX Connector then its started async using a single thread pool. This is not needed as the thread should be terminated after usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira