[jboss-jira] [JBoss JIRA] (WFCORE-1014) DefaultDeploymentOperations.getDeploymentsStatus doesn't consider model operation result outcome

RH Bugzilla Integration (JIRA) issues at jboss.org
Fri Oct 30 14:32:00 EDT 2015


    [ https://issues.jboss.org/browse/WFCORE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123995#comment-13123995 ] 

RH Bugzilla Integration commented on WFCORE-1014:
-------------------------------------------------

Vladimir Dosoudil <dosoudil at redhat.com> changed the Status of [bug 1266615|https://bugzilla.redhat.com/show_bug.cgi?id=1266615] from MODIFIED to ON_QA

> DefaultDeploymentOperations.getDeploymentsStatus doesn't consider model operation result outcome
> ------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-1014
>                 URL: https://issues.jboss.org/browse/WFCORE-1014
>             Project: WildFly Core
>          Issue Type: Bug
>    Affects Versions: 2.0.0.CR6
>            Reporter: Aaron Ogburn
>            Assignee: Aaron Ogburn
>             Fix For: 2.0.0.CR6
>
>
> The deployment scanner doesn't properly consider the  result outcome of its read child operation during getDeploymentsStatus().  This has bad consequences if the operation fails, for instance due to an OOME or possibly some other unexpected exception.
> The operation catches the exception and returns an empty result.  The deployment scanner misinterprets that empty result to mean there are no applications deployed and sets .undeployed marker files for all of them.  The deployment scanner should confirm if the operation was a success or not so we can avoid potential side effects of undeployed applications from an OOME.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list