[
https://issues.apache.org/jira/browse/ARTEMIS-4436?focusedWorklogId=881844&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-881844
]
ASF GitHub Bot logged work on ARTEMIS-4436:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Sep/23 08:40
Start Date: 26/Sep/23 08:40
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4628:
URL:
https://github.com/apache/activemq-artemis/pull/4628#issuecomment-1735090296
Yes, per my comment, I dont think it makes sense to remove notice that
clients/brokers-acting-as-clients lost connection just because the other side
was shut down 'cleanly'. This side still expected to be connected and no longer
is, thats detail they'll often want/need to know, regardless of whether the
other side went away intentionally (which, per my comment, I've seen people do
unwittingly on several occasions).
I agree a warning level message is excessive, but suppressing notice
entirely seems the wrong fix to that...I'd still report it happened, but at
Info level.
Issue Time Tracking
-------------------
Worklog Id: (was: 881844)
Time Spent: 1.5h (was: 1h 20m)
> Artemis is logging warnings during clean shutdown of server in cluster
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-4436
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4436
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.30.0
> Reporter: Emmanuel Hugonnet
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> If a node from a cluster shutdowns cleanly this shouldn't create WARN
> messages in the logs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
