You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2009/08/26 21:47:59 UTC
[jira] Closed: (FELIX-1478) Add shutdown hook to launcher to
cleanly shutdown the framework if the process is killed
[ https://issues.apache.org/jira/browse/FELIX-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-1478.
----------------------------------
Resolution: Fixed
Added shutdown hook to launcher which can be turned off with "felix.shutdown.hook=false".
> Add shutdown hook to launcher to cleanly shutdown the framework if the process is killed
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-1478
> URL: https://issues.apache.org/jira/browse/FELIX-1478
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: felix-1.8.1
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: felix-2.0.0
>
>
> As it stands currently (and dating back to the Oscar days), if someone does a control-C, then the framework process just dies and there is no attempt to shutdown cleanly. If we add a shutdown hook, then we can cleanly shutdown the framework.
> I am not sure if this would necessarily impact anyone who directly uses our launcher to launch the framework. I imagine there could possibly be an issue if someone uses our launcher, but registers their own shutdown hook. We also have the potential issue of a deadlock or some situation where we cannot exit, which could prevent the VM from exiting.
> Any one have any thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.