Hi Gayan, You can use following two properties,
max.delivery.drop max.delivery.attempts By enabling max.delivery.drop will drop the message after the initiated number of attempts and the message processor will not be deactivated. Hope this suits your requirement. Cheers, *Nadeeshaan Gunasinghe* Senior Software Engineer, WSO2 Inc. http://wso2.com +94770596754 | [email protected] | Skype: nadeeshaan.gunasinghe <#> <http://www.facebook.com/nadeeshaan.gunasinghe> <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> <http://nadeeshaan.blogspot.com/> Get your own email signature <https://wisestamp.com/email-install?utm_source=promotion&utm_medium=signature&utm_campaign=get_your_own> On Sat, Jan 13, 2018 at 3:42 PM, Gayan Gunawardana <[email protected]> wrote: > Hi ESB team, > > I followed instruction given in [1] to implement DLC pattern (EI 6.1.1). > However there is a small issue when message processor try to send message > to suspended endpoint. The issue is message processor goes to *inactive* > state when sending messages to suspended endpoint. Due to that reason rest > of the messages in dlc-store won't be delivered to expected endpoint. > > Appreciate any help regarding above issue. > > [1] https://docs.wso2.com/display/IntegrationPatterns/Dead+Letter+Channel > > Thanks, > Gayan > -- > Gayan Gunawardana > Senior Software Engineer; WSO2 Inc.; http://wso2.com/ > Email: [email protected] > Mobile: +94 (71) 8020933 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
