Hi Chamikra;
 
I think it wont enough that if you store only the RM related stuff in the DB , you have to save the context hierarchy some where , else the system wont be functioning as you required.

Thanks,
 Deepal
................................................................
~Future is Open~
----- Original Message -----
Sent: Tuesday, December 06, 2005 3:23 AM
Subject: Supporting permanent storage based reliability

Hi all,

I'm trying to implement failure safe reliability for Sandesha2. The idea is to allow a Axis2+Sadesha2 system to continue a reliable message sequence even after a failure (may be due to a sudden shutdown of Sandesha2, or may be due to power failure). Since Sandesha2 itself is going to be based on a database, it can protect its state from a crash.

However protecting the state of Axis2 system is a problem. It seems like to continue correctly Axis2 will need the contexts to come back with the same relationships and state ( flow information ect. ) it had before .

Does this mean that we have to ask axis2-devs to bring back the Context Hierarchy Serialization methods we agreed to remove from it sometime back. Or is there a better/different way?

Thanx,
Chamikara

Reply via email to