jms - Spring Integration message redelivery best practice -
I am currently working on an application with spring integration. Guaranteed delivery and option for application require that it will be functional for a certain time, which is unavailable without the external system lost. The channel will be supported with JMS finale. I would like to understand what is the best practice for reproduction with spring integration. We have the following options:
-
There are several outbound message gateways in the flow of integration of applications that require RPC calls with external systems Stateful retrieval advice can be used specific After reaching maximum attemps for runtime exceptions, the message will be addressed in the recovery channel. The recovery channel will use a delay and then send the message back to the original channel. After the X bar, this message will reach the Recovery Channel, this error channel will be addressed, where it will be logged without further processing. In this case, the delayed component should use the JDBC message collection option.
-
Another option would be to use the standard JMS option for delivery. In this case, the delivery policy will be applied on the JMS provider side, not on spring integration.
Which is the best practice for re-distribution of messages with spring integration?
I would say in such a way: the wheel has not changed again!
If there is a similar solution already on this matter, just use it as your specific configuration.
OK, if JMS is the solution, then go ahead. Need to deal with DLQ in case of end of message or re-delivery thrilling. But the concept is here.
Comments
Post a Comment