[
https://issues.apache.org/jira/browse/SMX4-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287402#comment-13287402
]
metatech commented on SMX4-744:
-------------------------------
The "osgi:reference" has one drawback : the referenced component (in this
example camel-jetty) cannot be hot-redeployed. Probably because once the OSGi
reference becomes invalid, the using bundles are waiting to rebind it, which
prevents the using bundles from being cleanly stopped (see log below).
{code}
OcsgiServiceProxyFactoryBean | Service reference
[[org.apache.camel.spi.ComponentResolver]] was unregistered and unbound from
the service proxy
OsgiServiceBindingUtils | Calling unbind on
org.springframework.osgi.service.importer.support.internal.aop.ServiceProviderTCCLInterceptor$ServiceProviderTCCLListener@1840879
w/ reference [org.apache.camel.spi.ComponentResolver]
RunnableTimedExecution | Closing runnable for context
OsgiBundleXmlApplicationContext(bundle=mycomponent,
config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider
taking a snapshot and then shutdown the VM in case the thread still hangs
{code}
> specify camel feature bundle start level less than 60
> -----------------------------------------------------
>
> Key: SMX4-744
> URL: https://issues.apache.org/jira/browse/SMX4-744
> Project: ServiceMix 4
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 4.4.0
>
>
> so that the camel related bundles always get started before end users
> bundle, this can avoid lots of asyn issues customer may encounter.
> More discussion from [1]
> [1]http://servicemix.396122.n5.nabble.com/DISCUSS-how-about-specify-camel-feature-bundle-level-less-than-60-td3334566.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
