Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <2119709887.1239303132949.JavaMail.jira@brutus>
Date: Thu, 9 Apr 2009 11:52:12 -0700 (PDT)
From: "Sahoo (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=12697600#action_12697600 ] 

Sahoo commented on FELIX-1027:
------------------------------

Stuart,

The classloader API changes are discussed at:
http://openjdk.java.net/groups/core-libs/ClassLoaderProposal.html

Thanks,
Sahoo

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