On Thu, Mar 19, 2009 at 8:48 AM, Christoph Jäger < christoph.jae...@polleninfo.org> wrote:
> I also have the same problem, searched the web, read lots of blog entries > and articles of how you can avoid it. The advice found basically is: > increase the memory available for the permgen, and do not redeploy your > application too often. > > Am I the only one who is not satisfied with this? In my opinion, the ever > increasing permgen memory consumption in the Sun JVM (I think it is only > 1.6, but maybe also 1.5) is a bug in the JVM design. > Well -- not a bug per se, but perhaps not well-suited to an environment where class generation and reloading is increasingly common. If you're not willing to move to a VM without a permanent generation, there is an option to collect from the permanent generation with the concurrent mark/sweep collector. You'd want to read into it in more detail to decide if it's right for your development environment, but it seems like a useful option: -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
