I'm afraid that this problem is unsolvable and there allways be situations in cluster, that after partition merge, cluster will be in inconsistent state and would produce wrong output.
No. Cases: - DRM: we refresh total view after merging
Agree.
- Http session: sticky sessions => the last state is always correct
Agree.
- SFSB: we always use the same node and the last state will be resent to other node at merge time
Disagree.
Consider following:
1. Cluster running banking application with SFSB's
2. Cluster is split into two groups
3. Each group continues concurently previous computation
4. Second group finishes computation and changes SFSB state and produces output (assigns money to account)
5. First group still doesn't finish its computation
6. Partition merge occurs
7. SFBS state on nodes of second group is rewriten by state of first unfished group
8. Cluster finishes computation again and changes SFBS state and produces output (assigns AGAIN money to account)
So we get as I belive incorrect and dangerous cluster behavior.
Greets David
-- http://www.sweb.cz/david.klimek
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
