You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2010/09/03 15:10:32 UTC
[jira] Updated: (ARIES-371) Add functionality to allow quiescing of
bundles
[ https://issues.apache.org/jira/browse/ARIES-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hughes updated ARIES-371:
--------------------------------
Fix Version/s: 0.2
(was: 0.1)
> Add functionality to allow quiescing of bundles
> -----------------------------------------------
>
> Key: ARIES-371
> URL: https://issues.apache.org/jira/browse/ARIES-371
> Project: Aries
> Issue Type: New Feature
> Affects Versions: 0.1
> Reporter: Philip Nickoll
> Assignee: Timothy Ward
> Fix For: 0.2
>
> Attachments: quiesce.txt, quiesce_manager_patch.txt
>
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> There is a need to allow bundles to quiesce gracefully such that in-flight threads in a replaced module are permitted to run to completion. This could allow updates to be made to applications without requiring them to be restarted. If a quiesce does not complete within a suitable time period (e.g. the time a blueprint reference waits), then we should forcefully stop the bundles! Note that this is not specific to blueprint but anyone that needs to be aware of the bundle lifecycle.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.