You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alasdair Nottingham (JIRA)" <ji...@apache.org> on 2011/07/15 01:33:59 UTC
[jira] [Created] (ARIES-709) Well behaved shutdown of the
application runtime
Well behaved shutdown of the application runtime
------------------------------------------------
Key: ARIES-709
URL: https://issues.apache.org/jira/browse/ARIES-709
Project: Aries
Issue Type: Bug
Reporter: Alasdair Nottingham
If you take the bundles required for isolated application runtime and then shut them down in the wrong order (and I don't know what the right one is) it can take 5 minutes to shutdown. This is because the ApplicationContextImpl.java in the isolated runtime in the uninstall method calls the BundleFrameworkManager and if that has gone away blueprint blocks for the default 5 minutes in the hope a replacement is coming.
Fixing this may be as simple as reducing the timeout, but that is probably only part of the solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (ARIES-709) Well behaved shutdown of the
application runtime
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham reassigned ARIES-709:
-----------------------------------------
Assignee: Alasdair Nottingham
> Well behaved shutdown of the application runtime
> ------------------------------------------------
>
> Key: ARIES-709
> URL: https://issues.apache.org/jira/browse/ARIES-709
> Project: Aries
> Issue Type: Bug
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
>
> If you take the bundles required for isolated application runtime and then shut them down in the wrong order (and I don't know what the right one is) it can take 5 minutes to shutdown. This is because the ApplicationContextImpl.java in the isolated runtime in the uninstall method calls the BundleFrameworkManager and if that has gone away blueprint blocks for the default 5 minutes in the hope a replacement is coming.
> Fixing this may be as simple as reducing the timeout, but that is probably only part of the solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-709) Well behaved shutdown of the
application runtime
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham resolved ARIES-709.
---------------------------------------
Resolution: Fixed
> Well behaved shutdown of the application runtime
> ------------------------------------------------
>
> Key: ARIES-709
> URL: https://issues.apache.org/jira/browse/ARIES-709
> Project: Aries
> Issue Type: Bug
> Reporter: Alasdair Nottingham
> Assignee: Alasdair Nottingham
>
> If you take the bundles required for isolated application runtime and then shut them down in the wrong order (and I don't know what the right one is) it can take 5 minutes to shutdown. This is because the ApplicationContextImpl.java in the isolated runtime in the uninstall method calls the BundleFrameworkManager and if that has gone away blueprint blocks for the default 5 minutes in the hope a replacement is coming.
> Fixing this may be as simple as reducing the timeout, but that is probably only part of the solution.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira