Caldarale, Charles R wrote: > > > It's also irrelevant. The heap size (-Xmx + -XX:MaxPermSize) must fit in > a contiguous area of virtual memory within the process. On a 32-bit > Windows system, the process space is 2 GB, unfortunately very fragmented > by DLLs that Windows insists on scattering throughout the area. You will > never be able to get a total heap larger than 1.2 - 1.5 GB. (There is a > boot-time switch in Windows Server to allow 3 GB user process space, but > that can cause other problems for the OS.) > > The above is not possible to achieve on a 32-bit system - ever. Shrink > the MaxPermSize down to something reasonable (e.g., 128m), then experiment > with -Xmx until the JVM loads. Normally best to set -Xms and -Xmx to the > same value. > > - Chuck > > >
Thank you both for replying. The architecture is indeed x86 (Windows 2003 server) and changing OS is not an option right now (going live soon). The strange thing is that if we place all 20 contexts in the Tomcat 6.0\webapps then we get this exception/error: ..backtrace.. Cause by java.lang.OutOfMemoryError: PermGen space. If we place the contexts outside of the Tomcat 6.0\webapps (updated server.xml ofc), then we DON'T get the OutOfMemoryError. Because we'd like to use the WAR update mechanism, keeping all webapps in Tomcat 6.0\webapps is preferred. -- View this message in context: http://www.nabble.com/MaxPermSize%2C-Tomcat-startup-trouble-tp23744089p23756562.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
