You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Chris Odom (JIRA)" <ji...@apache.org> on 2014/08/15 23:39:20 UTC
[jira] [Commented] (SMX4-1811) NMR and OSGI
[ https://issues.apache.org/jira/browse/SMX4-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099191#comment-14099191 ]
Chris Odom commented on SMX4-1811:
----------------------------------
LOG OUTPUT:
14:06:50,507 | INFO | FelixShutdown | BlueprintExtender | 9 - org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Destroying BlueprintContainer for bundle org.apache.servicemix.nmr.osgi
14:06:50,521 | INFO | FelixShutdown | BlueprintExtender | 9 - org.apache.aries.blueprint.core - 1.0.1.redhat-610379 | Destroying BlueprintContainer for bundle fuse-com-order-bundle
14:06:50,526 | INFO | FelixShutdown | BlueprintCamelContext | 142 - org.apache.camel.camel-core - 2.12.0.redhat-610379 | Apache Camel 2.12.0.redhat-610379 (CamelContext: comCamelContext) is shutting down
14:06:50,528 | INFO | FelixShutdown | DefaultShutdownStrategy | 142 - org.apache.camel.camel-core - 2.12.0.redhat-610379 | Starting to graceful shutdown 3 routes (timeout 300 seconds)
14:06:50,532 | INFO | 5 - ShutdownTask | DefaultShutdownStrategy | 142 - org.apache.camel.camel-core - 2.12.0.redhat-610379 | Route: orderReleaseAggregatorRoute shutdown complete, was consuming from: Endpoint[direct://orderReleaseAggregator]
14:06:50,945 | WARN | qtp205135738-140 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:06:55,945 | WARN | qtp205135738-140 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:00,946 | WARN | qtp205135738-138 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:05,947 | WARN | qtp205135738-141 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:10,951 | WARN | qtp205135738-141 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:16,042 | WARN | qtp205135738-140 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:20,948 | WARN | qtp205135738-138 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
14:07:25,950 | WARN | qtp205135738-138 | LogQuery | 59 - org.fusesource.insight.insight-log - 1.0.0.redhat-379 | No VmLogAppender available!
This repeats until the timeout occurs. And you can see the org.apache.servicemix.nmr.osgi bundle has already been removed.
> NMR and OSGI
> ------------
>
> Key: SMX4-1811
> URL: https://issues.apache.org/jira/browse/SMX4-1811
> Project: ServiceMix 4
> Issue Type: Bug
> Components: camel-nmr
> Affects Versions: 4.5.3
> Reporter: Chris Odom
>
> While shutting down Camel components that use NMR the org.apache.servicemix.nmr.osgi bundle is removed causing the NMR.unregisterEndpont to hang. The Camel Route will eventually shutdown after the timeout period occurs. I think there should be some dependency check so that if there are still registered endpoints that the underlying bundle does not shutdown.
--
This message was sent by Atlassian JIRA
(v6.2#6252)