You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@servicemix.apache.org by sandeep reddy <sa...@in2m.com> on 2008/10/29 16:21:50 UTC

How to maintain data consistency across different applications?

Hi Every body,

We are new to System integration technologies like Servicemix.

We are facing issues with "Reliability of data across different
applications".

Situation:

--- Http Consumer SU --- Bean-SU -- Routing-SU(using
camel) -- JMS Provider SU(topic)
Client App
\ | |

Response SU(Response)<--| |

JMS Consumer SU

Http Provider SU

ExternalApp

Message Flow:

1. From Client App message sends to Http Consume SU which sends to
Bean SU
2. From Bean SU sends to Routing SU and it delivers to JMS
Provider SU(topic) which is of MEP=in-only communication.
3. If message stores successfully to topic then Response SU sends
a success message back to client App.

Problem :

1. While sending success message back to if servicemix get
crashes then Client App will remain the same data( data which is there
before request initiated). But already message went to topic, JMS Consumer
SU will consume the message and send it to External Application.
2. Hence Client and External Applications will be under
inconsistent data.

How to handle these type of scenarios.

Thanks,
Sandeep.
--
View this message in context: http://www.nabble.com/How-to-maintain-data-consistency-across-different-applications--tp20229404p20229404.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.