----------------------------- Please read the FAQ! <http://java.apache.org/faq/> ----------------------------- > >The site runs on a dual processor sun box with a gigabyte of ram. Once > we > >started load testing, we found that the default configuration of apache > >produced a bottle neck because only one instance of the jvm was ever > >running, and thus only ever used one cpu. As a result, we configured > load > >balancing in order to run multiple jvms. > > Do you have any problems then with Session objects and sharing data. One > of the > advantages with the Servlet style of working is that your servlet is > loaded into one > JVM and then any data (usually in static variables) is accessible across > different connections. > > This way, you'd loose that ability and have things like counters and > variables > at different states through different JVM's (unless you wrote your code to > handle it specifically) ... > > Actually, the load-balancing code that comes with apache jserv only randomizes the first request to jserv instances. All subsequent requests are sent to the same jserv instance. The jserv code itself and the load balancing code in particular was nicely done. We've been extremely happy with it from the start of this project. (We started about 6 months ago) Brian Claus Application Development Specialist, Corelan Communications. -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html/> Problems?: [EMAIL PROTECTED]
