The Service Bus for the Connected Business
When a wcf service goes idle in IIS, it throws an error when the client tries to call it because of a timeout. We have neuron set up as a one-way datagram message to a wcf endpoint using a service connector. Is there a way to have neuron retry the call to the endpoint if it throws a timeout? I’m thinking since it is a one-way message neuron did its job by trying to send the message, but if there is a startup idle timeout, is there a way to detect this and try to do a retry (for one-way messaging).
Views: 394
you can apply a service policy to the service connector in Neuron and set the number of retries
We have a retry policy on it, it's just one retry, but if the message is retried and can't make it I would expect it to get audited to the failed audit log (which we have it set up to do on failure) I’m thinking it completes its action and the service connector believes it delivered the message because the wcf endpoint is up, but by the time the wcf throws a timeout, the service connector is not holding on to it anymore because it delivered it to a certain point. I think I could also just increase the timeout length on web config of the receiving wcf endpoint.
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
