Hi, What version of the Framework are you using ?
There have been a number of issues reported around acquiring locks in the framework. A few of them have been resolved in the latest framework release 4.0.3. Unless you are already using that version, you might give it a try. Otherwise, you might want to report an issue. BTW: Your treat dump didn't make it to the list. You might want to attach it to the JIRA issue if the problem persist with Framework 4.0.3. Regards Felix Am 29.08.2012 um 10:49 schrieb sugarcube: > I am experiencing a situation contending for acquireGlobalLock(). > > Consider two user bundles A and B in this scenario. B imports a class from > A. > When I uninstall bundle A (via fileinstall), it triggers a package refresh. > Since B depends on A, the refresh action leads to stop B. B uses Sping DM, > so it starts to close its application context and unregister the service > instance it exposed. while unregistering the service, the framework needs to > notify some service listener of the service changes. A resolve action is > then required when the service listener's bundle has dynamic-import > specified, in my case, the EventAdmin bundle. Spring dm then will not be > able to finish unregistering the service because of this second call of > acquireGlobalLock, until the thread doing package refresh times out on the > sync handling of bundle stopping event. > > > How do we understand this situation? where should we fix this problem? > felix, Sping DM, or EventAdmin? > > > See related stack trace below. > > > > > > -- > View this message in context: > http://apache-felix.18485.n6.nabble.com/Refreshing-package-causes-contending-for-acquireGlobalLock-tp4999027.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
