You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2009/04/23 10:35:49 UTC
[jira] Resolved: (FELIX-1027) deadlock with felix 1.6.0 ?
[ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall resolved FELIX-1027.
------------------------------------
Resolution: Fixed
Fix Version/s: felix-1.8.0
Assignee: Richard S. Hall (was: Karl Pauls)
I have committed my simple double-check patch. Please close this issue if you are satisfied. Thanks.
> 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
> Assignee: Richard S. Hall
> Priority: Critical
> Fix For: felix-1.8.0
>
> Attachments: deadlock.txt, deadlock_after_patch_FELIX_1027_20090406.log, FELIX-1027-double-check.txt, FELIX_1027_20090406.txt, test-deadlock.tgz
>
>
> 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.