[
https://issues.apache.org/activemq/browse/SMX4NMR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51141#action_51141
]
Freeman Fang commented on SMX4NMR-133:
--------------------------------------
Hi,
IMHO this deadlock would never happen.
The start level for kernel.management is 30 as specified in startup.properties
and the org.apache.servicemix.jbi.deployer bundle is installed within jbi
feature which means it's startlevel is 60
I can't see any chance the servicemix.deployer bundle could precede the
kernel.management bundle if follow our design.
I will close this issue first, feel free to reopen it if I'm wrong.
Thanks
Freeman
> 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.
