You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/11/27 16:35:00 UTC

[jira] [Commented] (ARTEMIS-4507) Make critical analyzer logging consistent

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

ASF subversion and git services commented on ARTEMIS-4507:
----------------------------------------------------------

Commit 7909f4b77f198eb1852156d8051d3a1a24367cc8 in activemq-artemis's branch refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=7909f4b77f ]

ARTEMIS-4507 make critical analyzer logging consistent


> Make critical analyzer logging consistent 
> ------------------------------------------
>
>                 Key: ARTEMIS-4507
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4507
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently if the {{critical-analyzer-policy}} is {{HALT}} or {{SHUTDOWN}} the log message is at {{ERROR}}. However, if the policy is {{LOG}} then the message is logged at {{WARN}}. All policies should log at {{ERROR}} to be consistent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)