[
https://issues.apache.org/jira/browse/BROOKLYN-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage resolved BROOKLYN-600.
--------------------------------
Resolution: Fixed
Assignee: Aled Sage
Fix Version/s: 1.0.0-M1
> Failed blueprint deployment: entities not cleaned up under-the-covers
> ---------------------------------------------------------------------
>
> Key: BROOKLYN-600
> URL: https://issues.apache.org/jira/browse/BROOKLYN-600
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Aled Sage
> Assignee: Aled Sage
> Priority: Major
> Fix For: 1.0.0-M1
>
>
> When a blueprint deployment fails, it can leave partially-created entities
> behind. These are referenced under-the-covers in
> {{LocalEntityManager.preRegisteredEntitiesById}} and
> {{preManagedEntitiesById}}, so are entirely hidden from the user. However, it
> is bad that we leave them around, and it was a contributing factor to
> https://issues.apache.org/jira/browse/BROOKLYN-599.
> For example, deploying this blueprint fails (because {{QpidQueue}} entity
> expects to have as a parent a {{QpidBroker}}).
> ```
> services:
> - type: org.apache.brooklyn.entity.messaging.qpid.QpidQueue
> ```
> However, the failed app/entity is still held in memory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
