the DLQ think should work also. but it's less portable. since we can't control the retries. in the approach that i described, we could think about adding the retry count to the job. (decrementing the counter on failed attempt would have to be done in a separate tx, and that's a bit clumsy) but then we can document the configurations. while with leveraging the JMS configuations, the configurations are JMS implementation specific. With the DLQ approach, the retry count has to be configured for the whole Queue, right ? If we use the jbpm-retry mechanism, then we can have the retry count defined in the process. Can you give a pointer as to why my proposed approach doesn't work ? Can it be made to work ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070839#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...