-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris,
On 7/16/12 9:54 AM, CRANFORD, CHRIS wrote: > When upgrading from 7.0.26 to 7.0.29, MyEclipse cannot start the > Tomcat instance without reaching an OutOfMemoryError exception that > results from a "GC overhead limit exceeded" when Tomcat begins > it's multi-threaded deployment process. MyEclipse is running with > 1GB of maximum memory and still errors with this exception where-as > reverting back to 7.0.26 and using only 512MB of memory, the > instance starts without any issues with plenty of memory to spare. > > > Have any others experienced this issue using Tomcat 7.0.29's > Multi-Thread deployment in UserConfig? > > Is there anyway to disable this feature globally? You got your question answered in another thread (the real problem is JAR scanning and metadata cashing taking up way too much memory: using metadata-complete="true" in web.xml should fix it) but I'll answer the question you asked, here, anyway. Globally, Tomcat's default is to use 1 deployment thread when starting a Host's contexts. See http://tomcat.apache.org/tomcat-7.0-doc/config/host.html, look for "startStopThreads". Tomcat will only do "true" parallel deployment if you explicitly set startStopThreads to some other value. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAFdE8ACgkQ9CaO5/Lv0PDzrwCghqXJHBFQg+/esZ8YsmPSglFj NV4AoJNExUjs1oNtIO+XQTZCJGtknnX9 =nY3H -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
