You should be able to cluster Tomcat without using multicast by having a
static members list with TCP pings to check the cluster nodes. You could of
course use exported resources to create the static members list.
Not sure about Glassfish but I'd expect it to be possible to do something
similar
Thanks for your replies.
mco is the solution I like. However AWS doesnt allow multicast, and hence I
figured I cannot succesfully cluster glassfish or tomcat in AWS!
On Monday, April 22, 2013 9:31:57 AM UTC+10, Shiva Narayanaswamy wrote:
My setup has an EC2 autoscaling group of clustered
I did an autoscaling pilot some months ago and I needed something similar
to this. For the pilot to work (far from the best solution), I was
triggering a puppet run on the server (DAS in your case) from the new
launched autoscaling instance, using mco as you noted if you have mco
working in
On Monday, April 22, 2013 12:31:57 AM UTC+1, Shiva Narayanaswamy wrote:
My setup has an EC2 autoscaling group of clustered glassfish application
servers. Each glassfish instance will register itself with a DAS (Domain
Administration Server) to become a member of the cluster, and deregister
