You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2009/10/28 10:24:10 UTC

[jira] Commented: (FELIX-1812) deadlock on System.exit()

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

Karl Pauls commented on FELIX-1812:
-----------------------------------

If you want calls to System.exit from a bundleactivator.start to work then you will have to disable the shutdown hook if you are using our launcher. This has nothing to do with the framework but with the shutdownhook in the launcher and that can be disabled. 

If you are seeing a deadlock in a call to systembundle.stop then this is an issue but it is not related to the shutdown hook and the system.exit. Please create a new issue and attach a stacktrace on that one where it shows that systembundle.stop does deadlock when called during startup from a bundleactivator.start and I will look into it. It can not be the same stacktrace as with the system.exit (as that is not being called anymore right :-)



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