if you're looking for functionality like load balancing, distributed sessions and sticky sessions, read through the docs at caucho.com. Their Resin J2EE container does a great job of handling this.
mike
if you're looking for functionality like load balancing, distributed sessions and sticky sessions, read through the docs at caucho.com. Their Resin J2EE container does a great job of handling this.
mike
Tomcat also has support for it and I think a lot of other servlet/applications containers have.Originally Posted by miikeeg
Just to add little more to the discussion. I was talking to a friend today, he told me he was asked about how does Spring deals with it. Suppose we have two servers, so we have 2 different ApplicationContexts, the singleton attribute for a bean is JVM level right (I know it's very complicated to achive singleton on multiple VMs). People here suggested Tomcat, Jboss, what if I have a standalone application the is built on top of Spring? Does spring has a support for jgroups or something like it, to replicate the application context?
afaik, it does not have this explicit clustering support. Of course, with its support for Remoting, JMS, and JMX and future context serialization, this could be added.
As was mentioned in this thread, Spring is not a server, so its understandable that out of the box this feature is not presently applicable.
No and I don't think it has to. Application contexts can be made available to a servlet context which I suppose can be made 'cluster-able' through the web container replication.
I'm pretty sure you can 'piggy back' on an existing mechanism - Spring is actually invisible to your application (no dependencies are enforced).
Costin Leau
SpringSource - http://www.SpringSource.com- Spring Training, Consulting, and Support - "From the Source"
http://twitter.com/costinl
Please use [ c o d e ] [ / c o d e ] tags