atom feed5 messages in org.torquebox.torquebox-userRe: [torquebox-user] Re: dead letter ...
FromSent OnAttachments
Carl HörbergJan 24, 2012 2:43 pm 
Carl HörbergJan 24, 2012 2:50 pm 
Benjamin BrowningJan 25, 2012 10:01 am 
Carl HörbergJan 25, 2012 11:30 am 
Benjamin BrowningFeb 1, 2012 5:54 am 
Subject:Re: [torquebox-user] Re: dead letter queue
From:Benjamin Browning (
Date:Feb 1, 2012 5:54:07 am

Yeah, we should update the docs.

The only way messages get delivered to the expiry queue is if you set a ttl when
publishing the message. See
and scroll down to "Table 7.2. Publish options" to read how to set ttl.

queue.publish('message', :ttl => 1000)


On Jan 25, 2012, at 2:30 PM, Carl Hörberg wrote:

oh, good to know!

maybe the docs should be updated, because now it says:

"If all of those attempts fail, the broker stores the message in a Dead Letter Queue (DLQ) that may be interrogated later."

which made at least me to believe that there was a DLQ configured :P

also, what's the difference between expiry and dead letter? timeout and exception? if so, how do i configure the timeout?

On Wed, Jan 25, 2012 at 19:02, Benjamin Browning <> wrote:

Note that the dead letter and expiry queues are queues like any other, so you
can write code to pull messages off them and resend them or do something else
with them.

Also of note is that unless you've modified the default dead-letter-address and
expiry-address in standalone.xml or created the appropriate DLQ or ExpiryQueue
queues, messages aren't being sent to either. The defaults configure these
values but don't create those queues so in effect dead letter or expired
messages get dropped vs building up in a queue somewhere.

On Jan 24, 2012, at 5:50 PM, Carl Hörberg wrote:

just found this:

so DLQ is on the todo list for Backstage. never mind then :)

how do i inspect the dead letter queue? can i somehow manually reissue them?