-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Leo,
On 1/11/2010 2:29 PM, Leo Donahue - PLANDEVX wrote: > org.apache.catalina.core.StandardWrapperValve invoke > SEVERE: Servlet.service() for servlet "servlet name" threw exception > java.lang.OutOfMemoryError: Java heap space To add to what others have said, getting an OOME can mean one of two things: 1. Your webapp simply needs more memory than you are allocating 2. You have a resource leak Most often, #2 is the culprit. Under what conditions are you getting the OOME? Lots of users after a short period of uptime, or all by yourself on your development environment after a long period of time? Do you keep a lot of information in users' sessions? How about in the application context? Does your webapp cache a lot of information? Do you use a database connection pool? If so, which one? What is the configuration? Does your webapp do anything that you expect to require very heavy memory consumption (image manipulation, in-memory representations of large datasets, etc.)? If so, you may simply need more memory to properly run your webapp. Finally, with a 32-bit JVM (you didn't say which you were using), you'll top-out around 2GiB for your heap no matter how much physical RAM you have. If you need more than 2GiB of heap, you'll need to go with a 64-bit environment. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktONOkACgkQ9CaO5/Lv0PAEMACfaS7G/FPgvCkEG1j4tS7mQkrC PkgAn3CYEh4D8eEa4FJdlLAIp7VmOIWZ =/cyT -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
