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/DLQ JMS Queue. This is tested with the jms_transacted quickstart.

<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.

1. Is this the intended behavior or a bug?
2. 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?
3. Is there a way to use the message store for the retries and DLQ instead of the actual JMS Queue.