[ 
https://issues.apache.org/jira/browse/ARTEMIS-4332?focusedWorklogId=869835&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-869835
 ]

ASF GitHub Bot logged work on ARTEMIS-4332:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Jul/23 15:49
            Start Date: 07/Jul/23 15:49
    Worklog Time Spent: 10m 
      Work Description: brusdev commented on code in PR #4526:
URL: https://github.com/apache/activemq-artemis/pull/4526#discussion_r1256038327


##########
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 testContextWithoutDebugTrackers() {
+      ExecutorService executor = 
Executors.newSingleThreadExecutor(ActiveMQThreadFactory.defaultThreadFactory(getClass().getName()));

Review Comment:
   done





Issue Time Tracking
-------------------

    Worklog Id:     (was: 869835)
    Time Spent: 2h  (was: 1h 50m)

> 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: 2h
>  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)

Reply via email to