Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1652135216.1239019573216.JavaMail.jira@brutus>
Date: Mon, 6 Apr 2009 05:06:13 -0700 (PDT)
From: "Stuart McCulloch (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
In-Reply-To: <1142464460.1239018253689.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stuart McCulloch commented on FELIX-1027:
-----------------------------------------

This certainly looks like a deadlock - and afaik there was some recent work done in this area which may have introduced this.
Do you happen to have a reproducible testcase? or even a smallish private testcase you could send to Richard and/or me?

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