[
https://issues.apache.org/jira/browse/ARTEMIS-4332?focusedWorklogId=868889&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-868889
]
ASF GitHub Bot logged work on ARTEMIS-4332:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jul/23 10:21
Start Date: 03/Jul/23 10:21
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4526:
URL: https://github.com/apache/activemq-artemis/pull/4526#discussion_r1250632007
##########
artemis-server/src/test/java/org/apache/activemq/artemis/core/persistence/impl/journal/OperationContextUnitTest.java:
##########
@@ -422,4 +422,43 @@ public void onError(final int errorCode, final String
errorMessage) {
Assert.assertEquals(0, operations.get());
}
+ @Test
+ public void testContextWithoutStoreOperationTrackers() {
+ ExecutorService executor =
Executors.newSingleThreadExecutor(ActiveMQThreadFactory.defaultThreadFactory(getClass().getName()));
+
+ OperationContextImpl.resetMaxStoreOperationTrackers();
Review Comment:
Slight nitpick but I think it would be better if it didnt do this reset
first, and so verified the default behaviour was as expected?
Issue Time Tracking
-------------------
Worklog Id: (was: 868889)
Time Spent: 40m (was: 0.5h)
> Add management method to close stuck server sessions
> ----------------------------------------------------
>
> Key: ARTEMIS-4332
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4332
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In rare cases a store operation could silently fails or starves, blocking the
> related server session and all delivering messages. Those server sessions can
> be closed adding a management method that cleans their operation context
> before closing them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
