[
https://issues.apache.org/jira/browse/CAMEL-10641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769791#comment-15769791
]
Claus Ibsen commented on CAMEL-10641:
-------------------------------------
The activator calls unload to late and CamelContext has been stopped/cleared
{code}
2016-12-22 12:06:44,015 | DEBUG | xFrameworkWiring | Activator
| 55 - org.apache.camel.camel-core - 2.19.0.SNAPSHOT | Bundle stopped:
org.apache.camel.camel-netty
2016-12-22 12:06:44,017 | DEBUG | xFrameworkWiring | Activator
| 55 - org.apache.camel.camel-core - 2.19.0.SNAPSHOT | Unloaded 0 type
converters from bundle: org.apache.camel.camel-netty [60]
2016-12-22 12:06:44,030 | DEBUG | xFrameworkWiring | Activator
| 55 - org.apache.camel.camel-core - 2.19.0.SNAPSHOT | Bundle started:
org.apache.camel.camel-netty
{code}
So its likely some weird classloading issues with OSGi with static methods or
something.
> camel-core - In OSGi should unload the loaded type converters when bundle is
> removed
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-10641
> URL: https://issues.apache.org/jira/browse/CAMEL-10641
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, osgi
> Reporter: Claus Ibsen
> Fix For: 2.19.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/camel-core-not-detecting-converters-on-bundle-restart-in-karaf4-tp5791503.html
> So even if the CamelContext instance itself is shutdown, then somehow type
> converters that are static method calls somehow are causing issues. We should
> instead attempt to unload the type converters when stopping.
> However we need to ensure that this is called after CamelContext is stopped
> because the type converters are still to be used during shutdown of Camel
> itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
