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 2022/04/14 22:05:00 UTC

[jira] [Commented] (ARTEMIS-3779) Critical IO Error to be logged as Error

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

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

Commit da5d5e504fd677d04640a2de2de7951f95f7139f in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=da5d5e504f ]

ARTEMIS-3779 Critial IO Exception logged as Error


> Critical IO Error to be logged as Error
> ---------------------------------------
>
>                 Key: ARTEMIS-3779
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3779
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.21.0
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.22.0
>
>
> An user asked me to log.error when a Critical IO error happens rather than WARN. as they filter Error logs on a main screen.
> I think it makes sense.. and it's easy enough to change.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)