AFAIK the expired message will be moved into the DeadLetterQueue. Since you're able to configure the DLQ it should be possible to do what you want (using AMQ5). There's an open issue with expired message not being processed until someone tries to consume them (The bug was AMQ-1112 I think). So since your using selectors on the queue I'm not sure whether this applies or not. I'd just give it a try.
Mario On 8/30/07, DominicTulley <[EMAIL PROTECTED]> wrote: > > Is there a way, either with filters or timeouts on queues, to get my hands on > any messages that have been sitting in the queue for "too long"? > > My situtation/plan is to have a queue with multiple consumers. Each > consumer will be using a selector to decide which messages to consume. > Under ideal circumstances, all messages will have a consumer that wants > them, but situations can arise where a message doesn't match any selector. > I would like to have some mechanism whereby I can spot that the message is > at the "front" of the queue but after n seconds still hasn't been consumed. > This allows me to arrange for a consumer to start dealing with that > particular message type. > > I looked at the JSMExpiration header which sounded about right, except that > on expiry the outcome is to destroy the message. I would love to be able to > ask the expiry processing to simply forward the message to another queue, > for instance. > > I appreciate any suggestions. > > Thanks, > > -Dominic > -- > View this message in context: > http://www.nabble.com/How-can-I-find-messages-that-have-been-unconsumed-for-%22too-long%22--tf4353227s2354.html#a12404218 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
