Thank you Tim Bain. I created a ticket
https://issues.apache.org/jira/browse/AMQ-7456
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
The messages with a delay header are delivered once, after the delay period,
as expected. But when they are rejected by the consumer, they just sit on
the queue and block all newer messages.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
*Redelivery policy *
I'm using Activemq *v5.15.8*
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello,
I am using AMQP clients to produce/consume from an activemq queue. The queue
has a redeliveryPolicy defined.
When a scheduled message (x-opt-delivery-delay header) is enqueued, and the
message is rejected by the consumer, these messages seem to exist on the
queue forever and block any fol
I'm using activemq with an amqp library. When a long running consumer
consumes a message, the message stays in the pending state until the
consumer "rejects" the message or the connection dies. Is there a way to
change this behavior, perhaps a timeout configuration ?
In other words, is it possibl
Thank you Tim. Same thing happens when messages are settled as "Modified",
activemq continuously retries the messages without respecting the redelivery
config.
Are there examples or documentation anywhere that detail how to get
redelivery working with python clients ?
--
Sent from: http://acti
I'm using qpid proton (python) to connect to activemq and receive messages. I
noticed that, whenever my client "releases" a message, activemq immediately
retries without incrementing the retry count and without respecting the
redelivery policy.
amq traces
INFO | jvm 1| 2018/08/14 10:14:3
