> 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 could deal with such "slow" consumers previously. Justin [1] http://activemq.apache.org/components/artemis/documentation/latest/slow-consumers.html On Wed, Aug 26, 2020 at 4:27 PM Christopher Pisz <christopherp...@gmail.com> wrote: > 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 <jbert...@apache.org> > wrote: > > > 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 > > message won't be available to other consumers, but it also won't be > removed > > completely from the queue. Once the consumer or the connection is closed > > then any messages in this state will be fully restored to the queue for > > other consumers to receive. > > > > > > Justin > > > > On Wed, Aug 26, 2020 at 2:57 PM Christopher Pisz < > > christopherp...@gmail.com> > > wrote: > > > > > 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? > > > > > >
