> can you elaborate a bit on what kind of synchronization problems you found?
We are relying heavily on in-memory caches for data. These are
implemented as application scope beans. ServletExec 2.2 does not
synchronize the creation of application beans, so if you start a server
that has a few hundred connections waiting to get data, you will most
likely end up with alot more instances of the application bean than you
expected. In our case, every caching bean also had its own housekeeping
thread, which caused even more problems. So we quite quickly ran out of
both memory and CPU, but only when we were starting the server under heavy
load.
However, I received a bugfix from New Atlanta today that has fixed the
problem, 2.2.1, I do not know if it is official yet.
/dml
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
