You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aleksey Sushko (JIRA)" <ji...@apache.org> on 2017/02/23 07:08:44 UTC
[jira] [Commented] (CAMEL-10880) Clear list components "direct-vm"
from another OSGI camelContext
[ https://issues.apache.org/jira/browse/CAMEL-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880020#comment-15880020 ]
Aleksey Sushko commented on CAMEL-10880:
----------------------------------------
And where is your decision about the removal of absolutely all components of "direct-vm"?
Other components live in their OSGi bundle. Now they do not have access.
> Clear list components "direct-vm" from another OSGI camelContext
> -----------------------------------------------------------------
>
> Key: CAMEL-10880
> URL: https://issues.apache.org/jira/browse/CAMEL-10880
> Project: Camel
> Issue Type: Bug
> Components: camel-core, osgi
> Reporter: Aleksey Sushko
> Priority: Minor
>
> First CamelContext create endpoint "direct-vm".
> Second CamelContext create ProducerTemplate to this endpoint.
> Several attempts to start and stop the second CamelContext lead to clearing the list of all registered components "direct-vm".
> See More Forum [Stop component "direct-vm" from another OSGI camelContext|http://camel.465427.n5.nabble.com/
> Stop-component-direct-vm-from-another-OSGI-camelContext-tp5794194.html].
> It shows the call stack. Trigger list cleaning. At the same time all the routes are still in the running.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)