Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agree with <a href="https://stackoverflow.com/a/20375102/365237">the answer above</a> in that you should really try to find what is actually filling your permgen, and I'd heavily suspect it's about some classloader leak that you want to find a root cause for.</p> <p>There's <a href="https://community.jboss.org/message/716191" rel="nofollow noreferrer">this thread</a> in the JBoss forums that goes through couple of such diagnozed cases and how they were fixed. <a href="https://stackoverflow.com/a/11735497/365237">this answer</a> and <a href="http://javabook.compuware.com/content/memory/problem-patterns/class-loader-issues.aspx" rel="nofollow noreferrer">this article</a> discusses the issue in general as well. In that article there's a mention of possibly the easiest test you can do:</p> <blockquote> <p>Symptom</p> <p>This will happen only if you redeploy your application without restarting the application server. The JBoss 4.0.x series suffered from just such a classloader leak. As a result I could not redeploy our application more than twice before the JVM would run out of PermGen memory and crash.</p> <p>Solution</p> <p>To identify such a leak, un-deploy your application and then trigger a full heap dump (make sure to trigger a GC before that). Then check if you can find any of your application objects in the dump. If so, follow their references to their root, and you will find the cause of your classloader leak. In the case of JBoss 4.0 the only solution was to restart for every redeploy.</p> </blockquote> <p>This is what I'd try first, IF you think that redeployment might be related. <a href="http://frankkieviet.blogspot.fi/2006/10/how-to-fix-dreaded-permgen-space.html" rel="nofollow noreferrer">This blog post</a> is an earlier one, doing the same thing but discussing the details as well. Based on the posting it might be though that you're not actually redeploying anything, but permgen is just filling up by itself. In that case, examination of classes + anything else added to permgen might be the way (as has been already mentioned in previous answer).</p> <p>If that doesn't give more insight, my next step would be trying out <a href="http://plumbr.eu/permgen" rel="nofollow noreferrer">plumbr tool</a>. They have a sort of <a href="http://plumbr.eu/every-leak-is-found-2" rel="nofollow noreferrer">guarantee on finding the leak for you</a>, as well.</p>
    singulars
    1. This table or related slice is empty.
    1. POG1 garbage collector: Perm Gen fills up indefinitely until a Full GC is performed
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USeis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWe don't usually redeploy our application without restarting JBoss, I really think now that the fact that the Perm Gen is getting filled up so quickly is because of how our application is implemented, G1 actually only helped to expose this problem to us.
      singulars
      1. PO
      1. USJose Otavio
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload