> Is there no way for me to limit the amount of time it can sit in
delivery, without the client closing?
Sure there is. Just configure slow-consumer detection as described in the
documentation [1].
I apologize if I misunderstood, but it didn't appear that you were asking
about how the broker coul
Is there no way for me to limit the amount of time it can sit in delivery,
without the client closing?
i.e What if the client receives messages but its processing threads are
hung?
On Wed, Aug 26, 2020 at 4:10 PM Justin Bertram wrote:
> In this situation (where a message has been dispatched to a
In this situation (where a message has been dispatched to a client but the
client has not yet acknowledged that message) the broker will mark that
message as being "in delivery." You can see this in the admin console, for
example, by looking at the "Delivering Count" of the queue in question. The
m
What is the expected behavior from Artemis if I
* Connect to Artemis using the STOMP protocol
* Subscribe to a queue specifying Client-Individual as my Ack mode
* Receive a message from the queue to which I subscribed
* Never send an Ack for it?
Check out the roadmap [1]. A *lot* of work has been done since this topic
was last discussed on the mailing list. At this point I think most, if not
all, of the features which aren't yet implemented are probably unnecessary.
As Gary mentioned, please elaborate on what features you still need (if
a
Hi Weihao Li,
Can you expand on the features that you require that are missing?
We are still committed to making migration as easy as possible.
Kind regards,
gary
On Wed, 26 Aug 2020 at 15:23, Weihao Li wrote:
> Hi,
>
> Sorry if this is not the correct mailing list.
>
> We are loyal Active MQ u
Hi,
Sorry if this is not the correct mailing list.
We are loyal Active MQ users for many years and we notice ActiveMQ Artemis is
released and we plan to migrate ActiveMQ 5 to ActiveMQ Artemis in the future.
But seems like ActiveMQ Artemis haven't reached the sufficient level of feature
with th
