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] Resolved: (FELIX-1812) deadlock on System.exit()
Date Fri, 30 Oct 2009 14:42:59 GMT

     [ https://issues.apache.org/jira/browse/FELIX-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Karl Pauls resolved FELIX-1812.

       Resolution: Fixed
    Fix Version/s: felix-2.2.0

As a side effect, FELIX-1816 makes it possible again to call System.exit inside an activator.start
method while the framework is still in the STARTING state. However, the framework will not
be shutdown when the jvm exits.

Please close this issue if the current trunk works for you.

> deadlock on System.exit()
> -------------------------
>                 Key: FELIX-1812
>                 URL: https://issues.apache.org/jira/browse/FELIX-1812
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-2.0.1
>            Reporter: Dennis Geurts
>            Assignee: Karl Pauls
>             Fix For: felix-2.2.0
>         Attachments: Activator.java, felix-framework-2.0.1.tar.gz, trace.log
> A deadlock occurs if System.exit() is called during startup of the Apache Framework.
> additional information:
> We call System.exit() during the BundleActivator.start(BundleContext) method. 
> I will include a stacktrace and an example felix framework for reproduction.

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

View raw message