permgen

问题 I ran drools decision table with 100 rules and it worked fine. But as soon as I increased the number of rules to 1000, I started getting permgen space error. I had to increase permgen to 256MB for my process to accommodate the 3000 rules. My concern is as I keep adding the rules, I might need more and more permgen. I am thinking of not using drools and develop a custom solution due to this issue. Is this correct observation or am I doing something wrong causing the perm gen space requirement

问题 I have 4G memory(64-bit). Currently, I use default memory setting in Eclipse IDE(JUNO). when I deploy the application on JBoss 7.1 I get Out Of Memory error. I would like to know memory ratio of heap memory and permgen memory ? Let say, if I set 1G memory for heap memory, permgen memory will be 512M, just example. If so, permgen will be 50% of heap memory. Could you provide the way for memory allocatation for them? Currently eclipse.ini -startup plugins/org.eclipse.equinox.launcher_1.3.0

问题 In order to decide if the jvm is likely to run into a permgen space shortage after the next redeplyoment I'd like to monitor the current permgen space usage before hand something like: set myPermGenThreshold = 0.51 (51%) currentlyUsedPermGenSize = (...ask the jvm here... say it's 0.6) if (currentlyUsedPermGenSize > myPermGenThreshold ) { (...restart tomcat...) } else { (...redeploy application...) } 回答1: The Memory MX Bean will give you all non-heap usage, of which the perm gen is a part. The

问题 I realized that any application which uses hibernate, fails to undeploy completely in Glassfish 2.1.1. Many classes remain in memory after the undeployment process, you can check it using jmap and jhat. I've done several tests, and figured out that only applications which had hibernate failed to have a clen undeploy process. My Database provider for Hibernate in all the cases were jTDS 1.2.5. You don't even need to run the application. If you just deploy, and instantly undeploy, you will

问题 I'm getting the following error when running a build in ant buildcallbacks.xml:39: org.sonar.runner.RunnerException: java.lang.OutOfMemoryError: PermGen space It's the part of the build where sonar runs over our code. Is there a way for me to know exactly where this error is coming from i.e is it the sonar server or the client etc ? Here is line 39 of my buildcallbanks.xml <sonar:sonar /> EDIT: I've tried increasing the permsize from the wrapper.conf within Sonar and I still get the same

问题 Following are the snapshots I took after executing perform GC from jvisualvm. and First image is Heap stats and 2nd one is perm gen stats. I am not able to understand when I did GC utilized heap size decreased(as expected) but the allocated size of permanent generation increased (though the utilized permgen size remained the same). What could be the possible explanation of such behavior? JVM arguments used -Xbootclasspath/p:../xyz.jar -Xbootclasspath/a:../abc.jar -Djava.endorsed.dirs=..

问题 Assuming a 64-bit JVM, is there any significant benefit to keeping MaxPermSize small? This is in the context of a Java EE application that is frequently redeployed, and has a classloader leak. As a medium-term workaround, it seems very reasonable to just bump up MaxPermSize to an absurd value - as long as it won't blow out the disk swap space. Because the undeployed app's code is nearly all unused (apart from that involved in the leak), it's paged out by the operating system. So the load on

问题 Assuming a 64-bit JVM, is there any significant benefit to keeping MaxPermSize small? This is in the context of a Java EE application that is frequently redeployed, and has a classloader leak. As a medium-term workaround, it seems very reasonable to just bump up MaxPermSize to an absurd value - as long as it won't blow out the disk swap space. Because the undeployed app's code is nearly all unused (apart from that involved in the leak), it's paged out by the operating system. So the load on

问题 I have been developing a website using grails and demo'ing it using Cloudfoundry. Grails and Cloudfoundry are awesome! The are easy to use with support from grails plugins and tools in STS. My app uses MySQL, MongoDB, SpringSecurity, and more. I have only used it with one user logged in and I periodically get java.lang.OutOfMemoryError: PermGen space I have increased the memory to 1G using the grails plugin. I tried to set JAVA_OPTS to increase the memory and this did not work. I am going to

问题 Glassfish sometimes fails to stop when the PermGen is full, in this case asadmin stop-domain domain1 doesn't work. In Glassfish 2.1.1 it would just sit there forever; in 3.x it times out after AS_ADMIN_READTIMEOUT . So I am now working on my Glassfish stop script that will kill/kill -9 it after a certain timeout to guarantee it gets stopped. To fully test this I need to reproduce this PermGen full scenario. How can I deliberately fill up PermGen? I'm currently using Java 1.7.0_45 if that