[jira] [Commented] (CAMEL-11002) Camel-Blueprint - failed container fails to remove JMX object

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user paoloantinori opened a pull request:

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

    CAMEL-11002 - Camel-Blueprint, prevent JMX re-registration in case of…

    … failed Context

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/paoloantinori/camel CAMEL-11002

Alternatively you can review and apply these changes as the patch at:

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1531
    
----
commit 274ae6827f5776de555add1ba3afd546e7c29a3e
Author: Paolo Antinori <pa...@redhat.com>
Date:   2017-03-13T12:44:50Z

    CAMEL-11002 - Camel-Blueprint, prevent JMX re-registration in case of failed Context

----


> 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
>
> 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)