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 2014/02/06 15:34:10 UTC

[jira] [Commented] (CAMEL-7144) Blueprint route not shutdown when using OSGi service processor

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

Claus Ibsen commented on CAMEL-7144:
------------------------------------

As its a toString on the osgi proxy that causes it to call the remote service that is no longer, then its a bit more tricky.

We could either
- avoid any toString calls, but then non OSGi proxied beans can't have toString description in logs etc as today.
- detect if its a proxy and avoid toString
- something else

> Blueprint route not shutdown when using OSGi service processor
> --------------------------------------------------------------
>
>                 Key: CAMEL-7144
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7144
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.12.2
>            Reporter: Dominik Kunz
>             Fix For: Future
>
>
> The route description uses .toString() when shutting down. This causes the shutdown to block if a proxied OSGi service is used as processor (in XML DSL <process ref="osgiService/>) and the service is not present at the time the route is shut down.
> See http://camel.465427.n5.nabble.com/Blueprint-route-not-shutdown-when-using-OSGi-service-processor-td5746114.html



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)