[
https://issues.apache.org/jira/browse/ARTEMIS-5890?focusedWorklogId=1003520&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1003520
]
ASF GitHub Bot logged work on ARTEMIS-5890:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Feb/26 16:36
Start Date: 04/Feb/26 16:36
Worklog Time Spent: 10m
Work Description: tabish121 commented on PR #6218:
URL: https://github.com/apache/artemis/pull/6218#issuecomment-3848496955
I've pushed a branch that simplifies the changes and accounts for the
various paths that are triggering WARN logging which reduces the amount of
change here. While the checks for the connection state were actually thread
safe they don't account for all the ways this could hit closed states.
https://github.com/tabish121/artemis/pull/new/ARTEMIS-5890
Have a look
Issue Time Tracking
-------------------
Worklog Id: (was: 1003520)
Time Spent: 1h 10m (was: 1h)
> Closing a connection while large message is being delivered could show
> exceptions in the log
> --------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-5890
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5890
> Project: Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.52.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> If you close a connection while the server still delivering large messages,
> you could see exceptions in the logs (IllegalArgumentException).
> The delivery thread should check the state of the connection before issuing
> more deliveries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
