would create.) If so, it
sounds like it might be for us. if not, I think we go down the route
@claus suggests.
Thanks for your input so far.
Cheers, Andrew
*Andrew Harmel-Law*
twitter: @al94781 http://twitter.com/al94781
blog: the-music-of-time.blogspot.com
flickr: flickr.com/photos
Hi there,
We have a situation in our route whereby, when we encounter an error in
processing an inbound message, we want to flag the original as Failed (in
a header) prior to further processing, and also generate a new message to
request a tidy up of resources the original failure may have left
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
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
Hi there,
I am using ActiveMQ 5.8.0 and Camel 2.10.4. I am reading
ExchangePattern.InOnly messages from a JMS queue, and want to expire those
which are not processed within a given time explicitly to a named dead
letter queue. The problem is I can't get things to expire.
I have the following
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
