I agree with Erwin. It seems like you'd be better served using the
synchronous
org.apache.activemq.artemis.api.core.client.ClientConsumer#receive(long)
[1] rather than using an asynchronous MessageHandler. If the call to
receive(long) returns null then you know the consumer did not receive a
messag
Arno,
It is a message-queue, the work may never be done as it is always possible that
new work is added later.
But otherwise, you would need to use a timeout while reading the message.
e.g. if no new message arrives within 5 seconds, then assume the work is done.
Instead of using "setMessageHand
Hi,
This is a beginners question. I am having a queue, with a bunch of work orders
and try to have aynchoun listeners to do
the workpackages. In the main thread I need to know when the workers are
actually done with the work. How do I know all
messages have been worked on?
Using Artemis 2.1.16,
This mailing list is probably the best way to reach the community. Please
open a Jira [1] and attach your test to reproduce the issue. Thanks!
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS
On Mon, Feb 8, 2021 at 7:20 AM Svetlana Undalova
wrote:
> Hi,
>
> I'm trying to reach you as
Hi,
I'm trying to reach you as I ran into an issue trying to use Apache Artemis
(2.16).
I have slow consumers and went with prefetch size = 0 which according to
docs results in pulling messages by the client. All works well if consumer
starts after messages are already in the queue, but if it beco
I resolved some issues with negative address sizes in 2.16.0, it
related to multicast wildcard addresses which could apply to advisory
messages.
https://issues.apache.org/jira/browse/ARTEMIS-2768
I would suggest moving to 2.16.0
There were also some known issues with openwire advisory support
re
