"CRANFORD, CHRIS" <chris.cranf...@setech.com> wrote: >The OOME I am getting is coming from Heap, and that's even giving >Tomcat >1GB of maximum heap. The instance seems to start successfully outside >of the MyEclipse environment; however inside MyEclipse it fails >miserably. The surprising part of this is that the instance has ran >with half that amount of maximum Heap Memory prior to 7.0.29 without >any >problems or issues with memory errors. > >As far as number of jars in the LIB folder, we only have just over 100 >jars totaling a max of 50mb. > >-----Original Message----- >From: Christopher Schultz [mailto:ch...@christopherschultz.net] >Sent: Saturday, July 14, 2012 12:13 PM >To: Tomcat Users List >Subject: Re: OOME while expanding a war with tomcat 7.0.29 but not with >tomcat 7.0.28 > >Alberto, > >On Jul 14, 2012, at 8:42, Alberto Aresca <alberto.are...@gmail.com> >wrote: > >> I've just upgraded my tomcat from version 7.0.28 to the newly >released >> 7.0.29 but while before my webapp was being expanded without any >> problem, now it is causing an OOME. >> >> Of course this can be easily fixed by increasing the heap size but >> before going forward in the upgrade i'd like to know if anyone else >> have been experiencing something similar or if something in the >> expansion implementation changed recently (i couldn't find anything >> in the release note) > >Can you provide any other information? Stack trace or heap dump? Is >this >regular heap or permgen? What are your heap settings? > >Is there anything else we should know about your web app? Do you have >500 jar files in your lib directory? Do you cache a large dataset on >startup? >> > >-chris >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org
Most likely the Jar scanning (which caches a lot of data during startup) is the cause. There is a patch to reduce the volume of cached data significantly in bugzilla at the moment. In the meantime, setting metadata-complete may help. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
