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 2019/01/22 07:25:00 UTC

[jira] [Commented] (CAMEL-13094) Context MBean not unregistered on startup failure

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

Claus Ibsen commented on CAMEL-13094:
-------------------------------------

I dont recall any startup changes like that. Do you have any reproducable project / unit test etc?
The only change is in camel-blueprint, and I would assume you are not talking about OSGi but eap/widlfly

> Context MBean not unregistered on startup failure
> -------------------------------------------------
>
>                 Key: CAMEL-13094
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13094
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Thomas Diesler
>            Priority: Major
>             Fix For: 3.0.0
>
>
> In Camel-2.23.x a failure to start the context would call ServiceSupport.doStop(). This is no longer the case. Instead, a CamelContextStartupFailureEvent is thrown and services that might previously has been started are never stopped.
> As a result or (side effect) the context MBean may remain registered if the startup failure occurred after its initial registration. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)