[
https://issues.apache.org/jira/browse/ARTEMIS-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459922#comment-17459922
]
Robbie Gemmell commented on ARTEMIS-3610:
-----------------------------------------
The point of having the send with CompletionListener is to get reliable async
send, so having the default configuring being to lie about that seems wrong, at
least for the persistent messages; the spec provides a door for a
still-unreliable behaviour to be driven through in cases where the spec
"permits a lower level of reliability" already, i.e cases it already has doors
in the sync send behaviour. It also notes though that firing onComplete means
the "message has been successfully sent with the same degree of confidence as
if a normal synchronous send had been performed", which wouldnt be the case
here if the normal sync send is actually blocking for persistent messages.
> Artemis's Core JMS 2 CompletionListener with persistent messages should work
> by default
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3610
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3610
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
>
> JMS 2 spec allow non-persistent messages sent to get CompletionListener's
> callback called without any response coming from the broker, but persistent
> ones should use CompletionListener relying on broker's responses.
> Right now if users won't configure confirmationWindowSize (that's -1 by
> default), they won't get *any* meaningful behaviour of CompletionListener
> both for persistent and non-persistent messages: we should provide a default
> configuration of confirmationWindowSize or just allow CompletionListener to
> work without configuring any, in order to let persistent messages to work as
> by JMS 2 spec.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
