[
https://issues.apache.org/jira/browse/AMQ-8324?focusedWorklogId=948461&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-948461
]
ASF GitHub Bot logged work on AMQ-8324:
---------------------------------------
Author: ASF GitHub Bot
Created on: 15/Dec/24 23:01
Start Date: 15/Dec/24 23:01
Worklog Time Spent: 10m
Work Description: kenliao94 commented on PR #1364:
URL: https://github.com/apache/activemq/pull/1364#issuecomment-2544155349
I just pushed a commit that uses a single-threaded Executor to perform the
async send, and have that background thread wait until the current async send
is finished. So application sender thread is not blocked (meet threading
restriction) and async send is done one at a time. This will preserve ordering
across the session "A session will only invoke one CompletionListener callback
method at a time. For a given MessageProducer or JMSContext, callbacks (both
onCompletion and onException) will be performed in the same order as the
corresponding calls to the asynchronous send method."
TODO: Need to add a few more tests.
Issue Time Tracking
-------------------
Worklog Id: (was: 948461)
Time Spent: 4h 40m (was: 4.5h)
> Implement JMS 2.0 MessageProducer CompletionListener methods
> ------------------------------------------------------------
>
> Key: AMQ-8324
> URL: https://issues.apache.org/jira/browse/AMQ-8324
> Project: ActiveMQ Classic
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 6.2.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> CompletionListener, etc
--
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
