aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (ARIES-768) Application manager can take 5 minutes to shutdown
Date Thu, 27 Oct 2011 12:08:32 GMT


Alasdair Nottingham resolved ARIES-768.

    Resolution: Fixed
> Application manager can take 5 minutes to shutdown
> --------------------------------------------------
>                 Key: ARIES-768
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Application
>    Affects Versions: 0.3
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
> I thought I had fixed this, but it seems that the application manager can still take
5 minutes to shutdown. The stack trace is:
>         at java.lang.Object.wait(Native Method)
>         at org.apache.aries.blueprint.container.ReferenceRecipe.getService(
>         at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(
>         at org.apache.aries.blueprint.container.ReferenceRecipe$
>         at Proxy76916cc6_8687_48e9_934d_a5102df76a23.uninstallBundle(Unknown Source)
>         at org.apache.aries.application.runtime.isolated.impl.ApplicationContextImpl.uninstall(
>         at org.apache.aries.application.runtime.isolated.impl.ApplicationContextManagerImpl.close(
> this is waiting for a replacement for the BundleFrameworkManager which never comes. I
added a bind/unbind reference listener to do this as the framework was shutting down, but
it turns out that we still try to call it during close. So I've updated the close method to
only uninstall if it isn't already uninstalled. This should fix the 5 minute issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message