aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-709) Well behaved shutdown of the application runtime
Date Sat, 23 Jul 2011 12:21:09 GMT

     [ 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

        

Mime
View raw message