FYI - the fix for this issue has been merged. It will be available in
ActiveMQ Artemis 2.32.0.
Thanks again for the report!
Justin
On Thu, Nov 30, 2023 at 11:46 AM Justin Bertram wrote:
> I've created ARTEMIS-4520 [1] to deal with this. Thanks for reporting the
> issue!
>
>
> Justin
>
> [1]
I've created ARTEMIS-4520 [1] to deal with this. Thanks for reporting the
issue!
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4520
On Wed, Nov 29, 2023 at 4:08 AM Андрей wrote:
> Hi Team,
>
> I am currently using "artemis-jakarta-client" 2.31.2 version
>
> I've stumbled into an
On 11/30/23 12:22, Justin Bertram wrote:
Tim, I think those are fair points. Ultimately I think the JavaDoc is
relatively ambiguous, although I tend to favor your interpretation.
To be honest I don't think it is, just read the first sentence and then
ignore the fluff following as that is mainly
Tim, I think those are fair points. Ultimately I think the JavaDoc is
relatively ambiguous, although I tend to favor your interpretation.
What does the Qpid JMS client do in this case?
BTW, I looked through the Jakarta Messaging TCK source code and I don't see
where this specific use-case is
On 11/29/23 16:15, Justin Bertram wrote:
It's not clear to me that this is a defect. The JavaDoc for
JMSContext.acknowledge() [1] says (in part):
This method has identical behaviour to the acknowledge method on Message.
A client may individually acknowledge each message as it is consumed, or
It's not clear to me that this is a defect. The JavaDoc for
JMSContext.acknowledge() [1] says (in part):
> This method has identical behaviour to the acknowledge method on Message.
A client may individually acknowledge each message as it is consumed, or it
may choose to acknowledge messages as an
Hi Team,
I am currently using "artemis-jakarta-client" 2.31.2 version
I've stumbled into an issue with client acknowledge mode when using JMS
API. Here's an example:
try (var factory = new ActiveMQConnectionFactory("", "",
JMSContext.CLIENT_ACKNOWLEDGE)) {
var
