[
https://issues.apache.org/jira/browse/AMQ-9853?focusedWorklogId=1003630&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1003630
]
ASF GitHub Bot logged work on AMQ-9853:
---------------------------------------
Author: ASF GitHub Bot
Created on: 05/Feb/26 10:55
Start Date: 05/Feb/26 10:55
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #1643:
URL: https://github.com/apache/activemq/pull/1643#issuecomment-3852789499
This seems more like a potential client bug the test was catching but no
longer will. Calling close from another thread is meant to wait for an in
progress onMessage delivery to complete, so there doesnt appear to be a
legitimate race in the original test code calling close after the latch was
tripped due to receiving the final message.
Issue Time Tracking
-------------------
Worklog Id: (was: 1003630)
Time Spent: 0.5h (was: 20m)
> ActiveMQJMS2MessageListenerTest race condition
> ----------------------------------------------
>
> Key: AMQ-9853
> URL: https://issues.apache.org/jira/browse/AMQ-9853
> Project: ActiveMQ
> Issue Type: Task
> Components: Test Cases
> Reporter: Jean-Louis Monteiro
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 6.3.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Race condition: ACKs are Async and Closing Consumer Too Early Skips Them. The
> broker's queue statistics (dequeueCount) are the only reliable
> synchronization point to confirm ACKs were processed
--
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
