felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
Date Mon, 06 Apr 2009 16:14:12 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696151#action_12696151

Pierre De Rop commented on FELIX-1027:

As far as I understand, the issue arises because I use class.forName from my Activators. The
first Activator.start() method invokes
class.forName from the "FelixStartLevel" thread, and the other class.forName is invoked concurrently,
from another thread which is 
started by the second activator.

I am actually struggling with some legacy code which is using Class.forName() ...
In any case, I think that using Class.ForName is definitely a poor practice in OSGi, and I
will try to work around this problem
by just replacing the Class.forName() with the OSGi Registry ...

So, if you think there is nothing to fix at all in the framework, may be I should close this
fault report ?

> 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, deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt
> I just came across a deadlock with the felix 1.6.0 candidate version for the next fwk
> 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.

View raw message