On Mon, 2010-12-06 at 07:49 -0800, fenbers wrote:
> But wouldn't consuming them just take them out of the queue for the current
> application/consumer? Wouldn't the messages still linger on AMQ for all the
> other clients?
>
> Mark
You may want to refer to the FAQ on how a Queue works in compari
But wouldn't consuming them just take them out of the queue for the current
application/consumer? Wouldn't the messages still linger on AMQ for all the
other clients?
Mark
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Change-Expiration-tp3072602p3074720.html
Mark,
AMQ is just an elaborate FIFO queue of messages. If you need to change the
expiration on a bunch of messages, use a client to consume them. Once
flushed, you'll need to re-submit them with modified parameters as
appropriate. You might be able to do all this within a transaction - I have
not
Greetings,
My client app creates a message with a 12-hour expiration and sends the
message to the broker. But later, from another client app, I want to
revise the expiration of the original message. Is this possible?
Or, if not possible, or too complicated, another option would be to
reset
