[
https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696073#action_12696073
]
Stuart McCulloch commented on FELIX-1027:
-----------------------------------------
See also: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4670071
Some deadlocks can happen with OSGi style classloading because of the spurious
synchronization on loadClassInternal, so as Karl just pointed out to me you
might still get an exception even with this patch - but the timing window
should be much narrower...
( BTW the solution chosen by Sun to support this sort of 'parallel class
loading' is to use a special API, but I can't seem to find the exact details at
the moment... )
> deadlock with felix 1.6.0 ?
> ---------------------------
>
> Key: FELIX-1027
> URL: https://issues.apache.org/jira/browse/FELIX-1027
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Environment: jdk1.5, linux
> Reporter: Pierre De Rop
> Priority: Critical
> Attachments: deadlock.txt, FELIX_1027_20090406.txt
>
>
> I just came across a deadlock with the felix 1.6.0 candidate version for the
> next fwk version.
> I have attached to this post the corresponding "kill -QUIT" output.
> Richard, is it really an framework deadlock ? This is strange because I am
> testing the trunk since one month and never noticed the problem ...
> /pierre
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
