currently I'm evaluating the Spring DM-Server for production use in my company.
I like to know, if it will be possible to set up a multiple machine cluster with virgo. We need session replication for the web bundles for fail-over.
I would be happy if there is someone who could help me with setting up a cluster with the current Spring-DM Server 2.0.2 I did not get it done. I achieved to enable the Cluster part in the configuration and start the server without an error, but the nodes don't communicate with each other. A simple pure Tomcat cluster on my the two test-machines work perfectly so I exclude any network errors.
We have not tested clustering or session replication with dm Server or Virgo. I know some people have mentioned attempting this on the dm Server forums, but I don't know how successful their attempts have been. However, we have not received bug reports or support issues around clustering.
I am trying to understand how does clustering work with bundles in Virgo. For example, I have a bundle that's computationally expensive. The typical job takes up 2 CPUs for 2 minutes. I have a JINI farm set up to handle these jobs.
My questions is:
Can Virgo somehow replace the JINI farm given that all the requests will be from a bundle deployed in Virgo?
How can I scale Virgo?
I may be asking the wrong questions or have the wrong ideas. Feel free to correct me.
Apart from inheriting Tomcat's clustering features, Virgo has no explicit support for workload balancing or grid computing. It should be possible to build these features into a Virgo application, but the onus will be on the application to provide those features.
If you spot any general features that would make this type of application more tractable in a Virgo setting, I'd be interested to hear. For instance, if you wrapped the JINI support in bundles, are there any problems that are particularly tricky in a Virgo environment?