[
https://issues.apache.org/jira/browse/ARTEMIS-5694?focusedWorklogId=986131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-986131
]
ASF GitHub Bot logged work on ARTEMIS-5694:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 07/Oct/25 13:42
Start Date: 07/Oct/25 13:42
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #5952:
URL:
https://github.com/apache/activemq-artemis/pull/5952#issuecomment-3376958485
I am converting this to a draft as I found a few scenarios where the
lineupContext could be called without calling the actual storage.. (after
exceptions)
Also I will make this to use CriticalAnalyzer
Issue Time Tracking
-------------------
Worklog Id: (was: 986131)
Time Spent: 1h (was: 50m)
> Lingering sessions after a storage timeout
> ------------------------------------------
>
> Key: ARTEMIS-5694
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5694
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.42.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.43.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We had reports of sessions not closing for an unkown situation, probably on
> storage.
> I am adding a timeout verification and adding extra logs in case this happens.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
