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 GitHub Bot (Jira)" <ji...@apache.org> on 2023/11/08 15:35:00 UTC
[jira] [Work logged] (ARTEMIS-4483) Log.warn messages with AMQP during regular closing of AMQP clients.
[ https://issues.apache.org/jira/browse/ARTEMIS-4483?focusedWorklogId=889528&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889528 ]
ASF GitHub Bot logged work on ARTEMIS-4483:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Nov/23 15:34
Start Date: 08/Nov/23 15:34
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4666:
URL: https://github.com/apache/activemq-artemis/pull/4666
This PR can only be merged after #4656 is merged.
Issue Time Tracking
-------------------
Worklog Id: (was: 889528)
Remaining Estimate: 0h
Time Spent: 10m
> Log.warn messages with AMQP during regular closing of AMQP clients.
> -------------------------------------------------------------------
>
> Key: ARTEMIS-4483
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4483
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.31.2
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As I was fixing ARTEMIS-4476, I realized why regular closes in AMQP are throwing log.warn in the log for cleaning up sessions and even invalid connections at certain points.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)