You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Volodymyr Zhabiuk (JIRA)" <ji...@apache.org> on 2009/03/25 15:52:44 UTC

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

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

Volodymyr Zhabiuk updated SMX4NMR-133:
--------------------------------------

    Summary: Deadlock when starting the org.apache.servicemix.jbi.deployer bundle  (was: Deadlock when starting org.apache.servicemix.jbi.deployer bundle)

> 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
>
> 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.