axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjaya Karunasena <sanja...@wso2.com>
Subject Re: [Axis2]Clustering: Processing a request before state is replicated
Date Sat, 19 May 2007 09:21:01 GMT
On Saturday 19 May 2007 12:19, Afkham Azeez wrote:
> Scenario:
>
> There are 2 nodes, N1 & N2 in a cluster. The 1st request from Client C1
> goes to N1. There is a state change in N1 due to this request. Before the
> state is replicated to N2, C1 sends another request which goes to N2. The
> result C1 gets is incorrect since N2 was in the old state.
>
> This happened to me when I ran two nodes on the same machine, and the
> client was also on the same machine. Can such a scenario take place in a
> production environment?
>
> Any idea how such a scenario can be handled? How do other clustering
> implementations handle such a scenario?

This is deffinitely a valid & frequent scenario in a prodcution environment. 

This is in the class of the session replication problem which requires some 
type of a transaction handling (Locking & roleback).

Do we have such capabilities in the Axis2 clustering implementation? 

/Sanjaya

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message