Re: Supporting permanent storage based reliability

[Chamikara Jayalath]

Hi Deepal,

Yes. You r right. We need some information from the context hierarchy. As you know our previous attempt was to save the whole context hierarchy and retrieve it back when we return (remember this includeded the ConfigurationContext and all the ServiceGroupContexts, ServiceContexts, OperationContexts and Messagecontexts under that, even the once that are not intended for RM related services).

The idea Jaliya propose seems to be a better one. It is to save the MessageContext very early in the handler chain (may be just after security). This way we can avaoid from saving the total context hierarchy and limit it to saving the SOAPEnvelope+Transport Info.  When the server restart after a recovery, RM Module can re-inject the necessary messages into the Axis2 Engine.

Thanks,
Chamikara

On 12/9/05, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:

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 -----

From: Chamikara Jayalath

To: sandesha-dev@ws.apache.org

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