<!-- Introduction to Message Forwarding Processor With max deliver attempt and drop
the message after max deliver attempt-->
<definitions xmlns="http://ws.apache.org/ns/synapse">
<endpoint name="StockQuoteServiceEp">
<address uri="http://localhost:9000/services/SimpleStockQuoteService">
<suspendOnFailure>
<errorCodes>-1</errorCodes>
<progressionFactor>1.0</progressionFactor>
</suspendOnFailure>
</address>
</endpoint>
<sequence name="fault">
<log level="full">
<property name="MESSAGE" value="Executing default 'fault' sequence"/>
<property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
<property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
</log>
<drop/>
</sequence>
<sequence name="main">
<in>
<log level="full"/>
<property name="FORCE_SC_ACCEPTED" value="true" scope="axis2"/>
<property name="OUT_ONLY" value="true"/>
<property name="target.endpoint" value="StockQuoteServiceEp"/>
<store messageStore="MyStore"/>
</in>
<description>The main sequence for the message mediation</description>
</sequence>
<messageStore name="MyStore"/>
<messageProcessor
class="org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor"
name="ScheduledProcessor" messageStore="MyStore">
<parameter name="interval">10000</parameter>
<parameter name="max.deliver.attempts">3</parameter>
<parameter name="max.deliver.drop">true</parameter>
</messageProcessor>
</definitions>
Execute the sample client a few times with the following command.
ant stockquote -Daddurl=http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl=http://localhost:8280/ -Dmode=placeorder
When you start to send request to synapse from client, you will see message forwarding processor without
getting deactivate it keep on processing. This is due to the message will be dropped from the message store after
the maximum number of delivery attempts are made, and the message processor will remain activated.
"max.deliver.drop" parameter would have no effect when no value is specified for the Maximum Delivery Attempts parameter.
If this parameter is disabled, the undeliverable message will not be dropped and the message processor will be deactivated.