camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11002) Camel-Blueprint - failed container fails to remove JMX object
Date Mon, 13 Mar 2017 12:49:41 GMT

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

ASF GitHub Bot commented on CAMEL-11002:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/1531


> Camel-Blueprint - failed container fails to remove JMX object
> -------------------------------------------------------------
>
>                 Key: CAMEL-11002
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11002
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint
>    Affects Versions: 2.18.2
>            Reporter: Paolo Antinori
>            Assignee: Andrea Cosentino
>             Fix For: 2.18.4, 2.19.0
>
>
> There is an issue with {{camel-blueprint}} lifecycle, similar to issue CAMEL-10411.
> In case of an issue with an endpoint configuration, like for instance a non existing
http endpoint {{uri="http://localhost:6000/"}}, the JMX object of the CamelContext, remains
registered, even if it shouldn't.
> Camel current code actually already unregisters it, in {{org.apache.camel.management.DefaultManagementLifecycleStrategy#onContextStop}},
triggered by {{org.apache.camel.support.ServiceSupport#start}} exception handling section.
> The reason why the MBean object stays registered, is because of {{BlueprintCamelContext}}
is still registered as an OSGi service listener, and {{org.apache.camel.blueprint.BlueprintCamelContext#serviceChanged}}
 is invoked, re-registering a new instance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message