[
https://issues.apache.org/jira/browse/FELIX-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019366#comment-13019366
]
Stephane Chomat commented on FELIX-2913:
----------------------------------------
The main thread waits and acquires a bundle lock for bundle 0 (the framework
felix) and waits in method setStartLevelAndWait(...).
Another thread wants add a bundle listerner with the bundlecontext of bundle 0
and waits the lock which is keeped by the thread "main".
This thread does:
Take the bundle 0 and take its bundle context and add a listerner with it. I
don't why but it used by org.apache.aries, DefaultWorker, line 86.
See
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.aries/org.apache.aries.util/0.3/org/apache/aries/util/internal/DefaultWorker.java
> Deadlock in some case
> ---------------------
>
> Key: FELIX-2913
> URL: https://issues.apache.org/jira/browse/FELIX-2913
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-3.2.0
> Environment: mac os x
> Reporter: Stephane Chomat
> Priority: Critical
>
> I met a deadlock problem with felix 3.2.0.
> There is no problem with felix 3.0.9
> A thread waits on m_bundleLockObject in method acquireBundleLock and
> m_globalLockThread is null and m_globalLockCount equals to 0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
