Hi everyone,
could someone clarify how does the retry step work?
I've tried to use it as a wrapper for the service endpoint, in order to ensure the success of the call for short term unavailability.
Basically I have set up the process steps as follows:
However, if the process call fails, the second time the process is invoked, the input message seems to be the output of the first iteration, and not the original message. I've tried to manage this with a push/pop of the message but it seems quite overkilling, I tought the retry was taking care of that.
Would you be able to clarify the behavior?
Thank you
Fabrizio
Let's try to bring back this issue...:-)
anyone that could explain how does the retry step work?
I'm trying to use the retry as shown in the picture.. just a wrapper for the ServiceEndpoint, but it doesn't work.
If the service fails, the second time it is called the message body will be the output of the first iteration, thus failing again.
I am not expecting this behavior, should I store the message in the context and retrieve it as first step of the retry block? (even tough I would expect this to be automatically implemented in the step... )
Thank you
Fabrizio
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by