Hi Juergen,
GCache never got finished.
The wadi clustering works but is for stateful beans and AFAIK it
provides only the state replication between cluster members and not
the client that supports failover. I hope Gianny will tell me if I'm
wrong about this :-)
We do have the kind of clustering you want but I'm not sure if its
documented. Basically the server cluster members maintain cluster
membership information using multicast hearbeats and the ejb client
maintains a list of servers and can change target server based on
availability.
There is an example of this at sandbox/failover and it used to work,
but AFAIK no one has tried running it for several months.
This would be a great thing to turn into a sample and make more public
and documented for 2.2.
thanks
david jencks
On Jul 15, 2009, at 8:34 AM, Juergen Weber wrote:
Hi,
what is the state of Geronimo's EJB clustering?
Basically I wonder if it is possible to have n Java application
clients that
address m servers that run stateless beans. A client should stick to a
server as long it is alive and transparently go to another one if it
is
dead.
Is this information here still current for 2.2?
http://cwiki.apache.org/GMOxDEV/test-drive-geronimo-ejb-
clustering.html
Or would GGache be the way to go?
http://cwiki.apache.org/GMOxDEV/geronimo-clustering-with-gcache.html
Thanks,
Juergen
--
View this message in context:
http://www.nabble.com/State-of-EJB-Clustering-tp24500428s134p24500428.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
