Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1159253205.1253685916092.JavaMail.jira@brutus>
Date: Tue, 22 Sep 2009 23:05:16 -0700 (PDT)
From: "Karl Pauls (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-1631) Implicit bootdelegation causes hang
 on android
In-Reply-To: <1950906438.1253685556048.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-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved FELIX-1631.
-------------------------------

    Resolution: Fixed

Our implicit bootdelegation detection assumes that if we walk a classloader.getClass.getClassloader() chain we will ultimately arrive at the bootclassloader which is represented by null. Apparently this is not true on android but at one point we get the same classloader for the next as the one we already have (i.e., we run into an endless loop). I commited a fix which makes sure we stop if we hit null or the same classloader again which seems to fix the issue.

> Implicit bootdelegation causes hang on android
> ----------------------------------------------
>
>                 Key: FELIX-1631
>                 URL: https://issues.apache.org/jira/browse/FELIX-1631
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-1.8.0, felix-1.8.1, felix-2.0.0
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>             Fix For: felix-2.2.0
>
>
> When felix is embedded inside an android app and a bundle triggers a classload which in turn hits our implicit bootdelegation then we run into an endless loop and hang. The workaround for now is to set "felix.bootdelegation.implicit=false".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.