[
https://issues.apache.org/jira/browse/AMQ-8324?focusedWorklogId=948031&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-948031
]
ASF GitHub Bot logged work on AMQ-8324:
---------------------------------------
Author: ASF GitHub Bot
Created on: 12/Dec/24 14:45
Start Date: 12/Dec/24 14:45
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1364:
URL: https://github.com/apache/activemq/pull/1364#issuecomment-2539155655
@kenliao94 - Yeah I think it's probably simplest to just do the one message
at a time thing (don't even have an option to turn it off). The new method
should be spec compliant so if we just go with blocking until the completion
completes that works. The main thing is to make sure the completion handler
still runs in a new thread (so use an executor, etc).
This is still not going to be slow, it will be as fast as the normal sync
API which is still quite fast, it just limits the concurrent sends until we can
handle ordering. It ends up just being similar to sync but allows using the
callback to handle which can be nice for some use cases.
As you said, we can just keep the existing API with current async behavior
so users can retain that if they want multiple concurrent sends and a future
update could handle ordering if we want to support multiple concurrent sends
for the new API.
Issue Time Tracking
-------------------
Worklog Id: (was: 948031)
Time Spent: 4h 20m (was: 4h 10m)
> 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 20m
> 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
