[
https://issues.apache.org/jira/browse/ARTEMIS-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782133#comment-17782133
]
Erwin Dondorp commented on ARTEMIS-4483:
----------------------------------------
[~clebertsuconic]
what error message codes does this apply to?
is it these two?:
{code:java}
2023-11-02 12:30:18,557 WARN [org.apache.activemq.artemis.core.server]
AMQ222107: Cleared up resources for session 6e9fbac0-796a-11ee-87c0-fe52de550f9b
2023-11-02 12:30:18,557 WARN [org.apache.activemq.artemis.core.server]
AMQ222061: Client connection failed, clearing up resources for session
6ea18f81-796a-11ee-87c0-fe52de550f9b{code}
and what does the updated version change? does it skip these messages, or make
it a lower level, or ...?
the referenced PR was just a little bit too extensive for me to predict the new
situation...
> 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
>
>
> 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.
> So, this is a complimentar task to ARTEMIS-4476. It will be part of the same
> git commit, but it's an unrelated issue that is going to be fixed altogether
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
