Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Tue, 1 Mar 2011 19:34:37 +0000 (UTC)
From: "Alasdair Nottingham (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: 
 <1265387890.5824.1299008077203.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2076984665.5748.1299006458165.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Resolved: (ARIES-591) Application isolation code doesn't
 cope properly with a warm start
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alasdair Nottingham resolved ARIES-591.
---------------------------------------

    Resolution: Fixed

> Application isolation code doesn't cope properly with a warm start
> ------------------------------------------------------------------
>
>                 Key: ARIES-591
>                 URL: https://issues.apache.org/jira/browse/ARIES-591
>             Project: Aries
>          Issue Type: Bug
>          Components: Application
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
>             Fix For: 0.4
>
>
> It appears like there is some kind of weird interaction issue between equinox and aries during a warm start which results in NPEs in blueprint.
> The NPEs come when blueprint tries to go into the shared bundle framework and application frameworks. This is a bug, somewhere, but given 
> we do not persist any knowledge between restarts I'll make us remove the frameworks on shutdown. As a result warmstart will look like coldstart.
> This isn't ideal and it would be good to cope, but this is good enough for now.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira