Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <8620966.85391280485037016.JavaMail.jira@thor>
Date: Fri, 30 Jul 2010 06:17:17 -0400 (EDT)
From: "Timothy Ward (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Assigned: (ARIES-371) Add functionality to allow quiescing
 of bundles
In-Reply-To: <31912272.85351280484915886.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Ward reassigned ARIES-371:
----------------------------------

    Assignee: Timothy Ward

> 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.1
>
>         Attachments: quiesce.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.