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

["Karl Pauls (JIRA)" <ji...@apache.org>]

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

Karl Pauls closed FELIX-1812.
-----------------------------

    Resolution: Invalid
      Assignee: Karl Pauls

Looking at the stacktrace it looks to me like you are calling System.exit() inside the Activator.start() method of one of your bundles. This is just nothing you should ever do but if so, then you basically have two options to make this work without the deadlock. 

1) You can disable the shutdown hook we have in our launcher by using -Dfelix.shutdown.hook=false

2) Do the call to System.exit() asynchronously i.e., fork another thread inside your activator to do the deed.

I will close this issue as invalid for now. Please reopen in case you disagree

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