[
https://issues.apache.org/jira/browse/ARTEMIS-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669275#comment-16669275
]
ASF GitHub Bot commented on ARTEMIS-2157:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/2404
ARTEMIS-2157 Extra information on CriticalAnalyzer and its components
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-2157
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/2404.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2404
----
commit 692c30a701374f28dceeb491ffcf5e16077a04dd
Author: Clebert Suconic <clebertsuconic@...>
Date: 2018-10-30T20:10:35Z
ARTEMIS-2157 Extra information on CriticalAnalyzer and its components
----
> Add Information on Paths for CriticalAnalyzer
> ---------------------------------------------
>
> Key: ARTEMIS-2157
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2157
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.6.3
> Reporter: clebert suconic
> Assignee: clebert suconic
> Priority: Major
> Fix For: 2.7.0, 2.6.4
>
>
> When the critical analyzer issues an action, it doesn't show any information
> on when the component failed.
>
> With this task I'm adding information on what path is causing the issue.
>
> In case of tracing logger active on
> org.apache.activemq.artemis.utils.critical (CriticalMeasure) some extra
> information will be placed into logger.warn.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
