[
https://issues.apache.org/jira/browse/ARTEMIS-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Nigro updated ARTEMIS-3610:
-------------------------------------
Description:
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 block OR reliably use the 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.
was:
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 block OR reliably use the 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
JMS 2 spec suggest re CompletionListener.
> 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 block OR reliably use the 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)
