Hi, > From: Oisin Kim [mailto:[EMAIL PROTECTED]
> 50-60 instances of different entities, we had been gettign [...] > 350 session > method calls (the one which creates the entity instances). I've seen this too. > There are two solutions to this problem: > 1) use commit-option C - this means all your beans are not cached. > 2) increase the initial/maximum size of the memory allocation pool I think, you can also specify the max cache size (in number of items?) in conf/standardjboss.xml: container-configurations/container-configuration/ container-cache-conf/cache-policy-conf/max-capacity While 2) is good, in my understanding it just delays the time until the out of memory condition. Heiko -- Bancotec GmbH EMail: [EMAIL PROTECTED] Calwer Str. 33 Telefon: +49 711 222 992 900 D-70173 Stuttgart Telefax: +49 711 222 992 999 Ein Unternehmen der Cellent AG http://www.cellent.de/ ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
