felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
Date Mon, 06 Apr 2009 20:05:13 GMT

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

Karl Pauls commented on FELIX-1027:
-----------------------------------

In regard to 1, yes it should be save as we do our own (more finegrained locking). Not sure
about 2. 

> 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
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.


Mime
View raw message