Hi Marcos, You can set the *max.delivery.attempts* to a very large number. There is no such method to avoid deactivation since it is required to maintain the order of messages.
[1] - https://docs.wso2.com/display/ESB490/Scheduled+Failover+Message+Forwarding+Processor Regards, Vinod On Thu, Dec 21, 2017 at 5:56 PM, Marcos Tarín Esteve < mta...@alfatecsistemas.es> wrote: > Hello > > > > When the backend is down, I would like to keep the Message Processor > active always without having to drop any pending message and without having > the necessity of reactivate the Message Processor manually. > > > > I don’t care how to achieve this configuration ¿Can you send an example? > > > > Thanks in advance > > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Vinod Kavinda Senior Software Engineer *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.* Mobile : +94 (0) 712 415544 Blog : http://soatechflicks.blogspot.com/ [image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
