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/11/01 17:41:59 UTC
[jira] Reopened: (FELIX-1812) deadlock on System.exit()
[ https://issues.apache.org/jira/browse/FELIX-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls reopened FELIX-1812:
-------------------------------
I re-open this issue as I really don't like the solution (and it makes various other cases fail). I will have to get back to this and fix it correctly by introducing timeouts or something. The result for this case would be the same I imagine but for now i will rollback.
> 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.