You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Grzegorz Grzybek (JIRA)" <ji...@apache.org> on 2015/07/20 10:21:04 UTC
[jira] [Commented] (CAMEL-8984) BlueprintCamelContext OSGi service
is not unregistered when context is stopped
[ https://issues.apache.org/jira/browse/CAMEL-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633156#comment-14633156 ]
Grzegorz Grzybek commented on CAMEL-8984:
-----------------------------------------
In camel-test-blueprint tests I had problems with two separate ({{camel-1}} and {{camel-2}}) camel contexts available as OSGi services. When config admin configurations where updated twice, I had 3 services.
> BlueprintCamelContext OSGi service is not unregistered when context is stopped
> ------------------------------------------------------------------------------
>
> Key: CAMEL-8984
> URL: https://issues.apache.org/jira/browse/CAMEL-8984
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.15.2
> Reporter: Grzegorz Grzybek
> Assignee: Grzegorz Grzybek
>
> {{org.apache.camel.core.osgi.OsgiCamelContextPublisher}} doesn't receive {{CamelContextStoppingEvent}} because {{org.apache.camel.util.EventHelper#doNotifyEvent()}} checks for {{started}} state and {{org.apache.camel.core.osgi.OsgiCamelContextPublisher}} is never started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)