If using default connection configuration, you can ask the connection whether a temporary destination is still valid:
ActiveMQConnection.isDeleted(<temp dest>) Of course this is an activemq specific API.. Alternatively you could have a camel route watch the advisory messages to see when a temp dest gets deleted, then consume and ack all messages that match a selector with the JMSReplyTo being that deleted dest... might be other options, but those come off the top of my head On Fri, Apr 5, 2013 at 12:21 PM, SledgeHammer <gro...@firstam.com> wrote: > So there is no way to handle this except trying to send the response and > catching the exception? This is not good in my scenario because processing > a > message can take up to 1 minute. I can't use TTL because if the queue is > backed up, I do not want messages to die. Only time I want the messages to > die is when the ReplyTo address goes bad. That seems like a useful > scenario. > Otherwise, I might have to do 1 minute of work on thousands of messages > when > the producer isn't even there anymore. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Purge-policy-not-working-tp4665624p4665630.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
