ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-508) When rolling back the cause is not shown in the target's log
Date Thu, 15 Jan 2015 15:59:35 GMT

    [ https://issues.apache.org/jira/browse/ACE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278853#comment-14278853
] 

Marcel Offermans commented on ACE-508:
--------------------------------------

Correct, the agent running on the target will use the LogService if that is available locally.
So if you use the ace-launcher.jar with the -v option, or have some other means to view the
log, you can see such information there.

The audit log in ACE however only logs "success: false" when a deployment package installation/update
fails. Adding the cause would make sense, as that indeed gives people looking at the audit
log on the ACE server (through the UI or some other means) a better overview of what is going
on. If we can add the cause to the event as a property and then record that extra property
in the audit log, that should be enough.

> When rolling back the cause is not shown in the target's log
> ------------------------------------------------------------
>
>                 Key: ACE-508
>                 URL: https://issues.apache.org/jira/browse/ACE-508
>             Project: ACE
>          Issue Type: Improvement
>            Reporter: Alexander Broekhuis
>            Priority: Minor
>
> Currently the Log of a target will show that deployment of a package has failed, but
it does not show a cause or reason of the failure.
> For resolving the problem, this is needed. 
> For example, if a ResourceProcessor fails with a ResourceProcessorException, that exception
including the message could be added to the log.



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

Mime
View raw message