Hi all, I just thought I'd share this with the group in case anyone else runs into the same problem.
We have small ear deployed on JBoss with <50 Entities < 50 Session Beans. >From the Session Fa�ade we do a create which in turn will create about 50-60 instances of different entities, we had been gettign java.lang.outOfMemory Excpetion thrown when we got to about 350 session method calls (the one which creates the entity instances). 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 (2) is much more favourable (if you have the memory spare), as it allow better caching of your entities. The line to change in the run.bat file is set JAVA_OPTS=%JAVA_OPTS% -Xms32m -Xmx256m -Dprogram.name=%PROGNAME% This sets the initial stack size to 32MB and the max to 256MB, of course if you can afford more then make the sizes bigger! Hope this helps someone, Oisin Oisin Kim Aurium Tel: +353 1 6611132 Fax: +353 1 6615200 e-mail: [EMAIL PROTECTED] web site: http://www.aurium.net ------------------------------------------------------- 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
