[richfaces-issues] [JBoss JIRA] Commented: (RF-7911) OutOfMemory when redeploying - ClientSelection not unregistered from PropertyEditorManager
[
https://jira.jboss.org/jira/browse/RF-7911?page=com.atlassian.jira.plugin...
]
Hans Cappelle commented on RF-7911:
-----------------------------------
I stumbled upon this issue looking for a solution on a similar PermGen OutOfMemoryError
but on another Application Server: GlassFish.
org.richfaces.model.selection.ClientSelection was also listed in the classes left behind
after undeploying the application. I noticed it was also linked to
org.apache.commons.io.FileCleaner of which the API states that it can cause this problem:
from: http://commons.apache.org/io/api-1.4/org/apache/commons/io/FileCleaner.html
In an environment with multiple class loaders (a servlet container, for example), you
should consider stopping the background thread if it is no longer needed. This is done by
invoking the method exitWhenFinished(), typically in
javax.servlet.ServletContextListener#contextDestroyed or similar.
You can find the original issue at: http://issues.apache.org/jira/browse/IO-99
Not sure if this can help you but would be great if you could point this out ;-).
OutOfMemory when redeploying - ClientSelection not unregistered from
PropertyEditorManager
------------------------------------------------------------------------------------------
Key: RF-7911
URL: https://jira.jboss.org/jira/browse/RF-7911
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.1
Environment: richfaces.3.3.1.GA + Tomcat 6
Reporter: Geert Coelmont
Attachments: screen_shot1.jpg, screen_shot1.jpg
When redeploying, webapp classloader isn't garbage collected, causing a
"java.lang.OutOfMemoryError: PermGen space" after a few times.
I used a profiler ("yourkit") to see where the issue was and found these 3
classes:
- org.richfaces.model.selection.ClientSelection
- com.sun.faces.application.ConverterPropertyEditorFactory$DisposableClassLoader
- com.sun.faces.application.ConverterPropertyEditorBase
See attached screen shot for more details.
I don't know where the 2 com.sun.faces classes come from either, but at least
org.richfaces.model.selection.ClientSelection shouldn't be there.
I saw issue RF-1284 which appears to be very similar, only now this happens in a newer
version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira