This is most likely due to some code you wrote. Most likely, your code is creating objects that can't be garbage collected for some reason.
A quick google brought up this link:
http://blogs.oracle.com/fkieviet/entry/classloader_leaks_the_dreaded_java
Announcement
Collapse
No announcement yet.
X
-
Did you read my previous post? You're running out of PermGen space, not the JVM's application memory heap.
Leave a comment:
-
as of now we have -Xms512m -Xmx2048m and as soon as it reached that max size it it OutOfMemory . But 2048 is huge. and every time we get the OutOfMemory at the DataSourceLoader.Is there a way we can collect some logs?
Leave a comment:
-
Try increasing the JVM's MaxPermSize.
Eg
You're running out of MaxPermSize which is memory taken by class metadata and based on your application (number of classes, use of proxies, Hibernate etc) you will need to adjust this value.Code:-XX:MaxPermSize=256m
Leave a comment:
-
No, there are currently no known memory leaks in the framework. Let us know if you put together data that suggests there may be one.
Leave a comment:
-
Memory Leak
SmartGwt power 2.4
Jan 27, 2012 2:30:54 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet DataSourceLoader threw exception
java.lang.OutOfMemoryError: PermGen space
Now a days we see the above messages very often in our logs.Are there any memory leaks in the frameworkTags: None
Leave a comment: