felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Geurts (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-1812) deadlock on System.exit()
Date Fri, 30 Oct 2009 19:35:59 GMT

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

Dennis Geurts closed FELIX-1812.

Excellent, this is what I want. 

As a sidenote:

Calling System.exit() during activation of a bundle is not something we do regularly ;-).
In this specific case, the bundle calling
System.exit() is part of a more elaborate licensing scheme. If we detect a situation where
no valid license can be obtained, we really
_do_ want to (be able to) exit the java process immediately. It is therefore sub-optimal to
say the least to delay the exit until after the complete framework
has come up, or to delegate this to another thread (for obvious reasons).

Great that this functionality has become been made  available!

> 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