Dead Letter Queue Handling in JBoss SOA-P
Issue
- Our experience in testing an async service is that if a Runtime exception is thrown in the action pipeline, the message is re-tried per the below configuration in the service and the message is placed and we can see it on the actual
jboss.messaging.destination.Queue/DLQJMS Queue. This is tested with thejms_transactedquickstart.
<activation-config>
<property name="dLQMaxResent" value="3"/>
</activation-config>
- If we change the exception thrown to a checked exception, all retry logic is ignored and instead the message is placed in the message store database with a DLQ classification and nothing in the JMS
Queue/DLQ.
- Is this the intended behavior or a bug?
- Is there a way to enable the re-try logic for a checked exception or do we always have to catch and re-throw as a runtime exception?
- Is there a way to use the message store for the retries and DLQ instead of the actual JMS Queue.
Environment
- Red Hat JBoss SOA Platform (SOA-P)
- 4.x
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
