Brilliant. Thanks very much @ceposta. I'll try it now and post back
(hopefully with a )
Cheers, Andrew
--
View this message in context:
http://camel.465427.n5.nabble.com/Not-Expiring-JMS-Messages-with-ActiveMQ-Camel-tp5732841p5732900.html
Sent from the Camel - Users mailing list archive at N
Andrew,
Maybe try setting your prefetch to 1 to see if the rest of the messages
expire. Prefetch is basically a batch delivery to the consumer, with 1000
messages being default for queues. If messages are prefetched to the
consumer then they cannot be expired (unless should have already been
consid
OK, as I posted earlier, I can see the broker trying to expire messages, but
nothing seems to expire. Is it because things as listed as "inflight"? (See
below) I'm aware that my unit test harness might not be entirely realistic.
Can anyone point out anything dumb I'm doing?
The inbound message h
Hi @ceposta,
I've just put that line in my config and I can now see ActiveMQ saying
"queue://fulfillmentRequest expiring messages ...". My test is still
failing, but it's probably because I'm being an idiot somewhere. Thanks for
your help.
I'll post back the eventual outcome
Cheers, Andrew
It seems you're expecting the broker to expire the messages?
By default the expiration task for a queue will run every 30s.. if your
test is taking less time than that, you'll want to tune the broker to check
for expiration a little sooner:
On Mon, May 20, 2013 at 5:04 AM, al94781 wrote:
> Hi
