Skip to content
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.

OSGi runtime suffers from deadlocks #173

Open
erdalkaraca opened this issue Aug 12, 2016 · 2 comments
Open

OSGi runtime suffers from deadlocks #173

erdalkaraca opened this issue Aug 12, 2016 · 2 comments

Comments

@erdalkaraca
Copy link

Hi,
I cannot extract a reproducible example to prove this, but just by including the publisher bundle in my (Eclipse) product and launching it, the OSGi runtime complains:

Getting a lock required more than 10000 ms. There might be a synchronization problem in this callstack or just the build/dispose process of some components took too long!

Whenever I start the product without the publisher, the (equinox) application starts (as expected).

I think this is a classloader issue.
Did anyone else encounter this behavior?

@BryanHunt
Copy link
Collaborator

I run this framework all the time and I haven't seen this problem.

@erdalkaraca
Copy link
Author

@BryanHunt can you try with this classloader setting:

-Dorg.osgi.framework.bundle.parent=ext

If I remove that setting, the application starts.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants