WSO2 ESB scheduled message forwarding processor becomes inactive after reaching max delivery attempt

0
votes

I tried to follow this link , and I did it step by step for four time, for the first 3 times I used WSO2 MB as a broker, and the last time I tried Apache ActiveMQ but the problem is, when I shut down SimpleQuoteService server and send messages to the proxy via SoapUI , they accumulate in my queue and my scheduled message forwarding processor becomes inactivated after reaching max delivery attempts but WSO2-ESB documentation is sayinq : "To test the failover scenario, shut down the JMS broker(i.e., the original message store) and send a few messages to the proxy service. You will see that the messages are not sent to the back-end since the original message store is not available. You will also see that the messages are stored in the failover message store."

Anyone to explain?!!!

1
wso2activemqwso2esbwso2mb

1 Answers

2
votes

You can disable deactivating the message processor setting "max.delivery.drop" parameter to 'Enabled'. It will drop the message after max delivery attempts without deactivating the processor. See here for docs(definitions) of these parameters.