camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5656) JMXConnector is started async, should terminate thread after started to avoid keeping around
Date Thu, 27 Sep 2012 13:42:07 GMT

    [ 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

Mime
View raw message