You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Jonathan Gallimore (JIRA)" <ji...@apache.org> on 2016/02/08 14:36:39 UTC

[jira] [Resolved] (TOMEE-1705) Destroy application attempts to initialize lazily loaded resources

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

Jonathan Gallimore resolved TOMEE-1705.
---------------------------------------
    Resolution: Fixed

> Destroy application attempts to initialize lazily loaded resources
> ------------------------------------------------------------------
>
>                 Key: TOMEE-1705
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1705
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.0-M1, 1.7.3
>            Reporter: Jonathan Gallimore
>            Assignee: Jonathan Gallimore
>             Fix For: 7.0.0-M2, 1.7.4
>
>
> If an application defines multiple resources, and one of the resources fails to start, the application is undeployed (as it should be), but when trying to undeploy the application, TomEE will lookup other resources to undeploy. The lookup will cause those resources to initialize and potentially throw confusing exceptions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)