Hi Chamikara and all I was thinking this sometimes back and had this kind of idea. Need to clarify regarding the feasibility with other modules. If we need to provide failure safe RM then we need to store messages. So if we store them just after the transport level with some id then in a crash, RM can make that message to inject into axis2 engine at the module initialization method. (That is why we add the module init method in the initial design of Axis2) Since we store messages before they get processed, we do not want to store the context information( assume that RM store everything in a DB)
Please comment. Thanks, Jaliya ----- Original Message ----- From: Chamikara Jayalath To: [email protected] Sent: Tuesday, December 06, 2005 6: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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
