[jira] Reopened: (SMX4NMR-133) Deadlock when starting the org.apache.servicemix.jbi.deployer bundle

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/SMX4NMR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet reopened SMX4NMR-133:
-------------------------------------


I can't think of any good reason to start this spring powered bundle synchronously.
Starting it asynchronously will lead to a much better interoperability when the NMR is not deployed on ServiceMix Kernel where we control the start level of all bundles.

> Deadlock when starting the org.apache.servicemix.jbi.deployer bundle
> --------------------------------------------------------------------
>
>                 Key: SMX4NMR-133
>                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-133
>             Project: ServiceMix NMR
>          Issue Type: Bug
>            Reporter: Volodymyr Zhabiuk
>            Assignee: Freeman Fang
>
> org.apache.servicemix.jbi.deployer bundle has  a
> {code}
> Spring-Context: *;publish-context:=false;create-asynchronously:=false 
> {code}
> statement in the manifest mf. Also it has a reference to the mbean server service. When the servicemix.deployer bundle precedes the kernel.management bundle, the application context for the deployer is not created until the mbean server reference is resolved. Because of the create-asynchronously:=false,  kernel.management context is waiting for the deployer bundle to be created. That's why we have a deadlock

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.