[
https://issues.jboss.org/browse/RF-13071?page=com.atlassian.jira.plugin.s...
]
Lutz Ulrich commented on RF-13071:
----------------------------------
I guess it's a warning, too.
Probably Tomcat logs such warnings whenever a wep application starts threads but won't
stop them.
For example {{org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.start()}}
starts 'push-session-manager-thread'-s.
These threads run a {{while(true)}} loop, and I guess they never terminate.
You should terminate these threads when the web application is stopped.
Undeploying Showcase from Tomcat6/7 can cause memory leak
---------------------------------------------------------
Key: RF-13071
URL:
https://issues.jboss.org/browse/RF-13071
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll, showcase
Affects Versions: 4.1.0.Final, 5.0.0.Alpha1
Reporter: Juraj Húska
Priority: Minor
Labels: memory_leak, performance
Fix For: 5-Tracking
When undeploying showcase from Tomcat 6/7 then following log is present on the server
console:
{code}
SEVERE: The web application [/richfaces-showcase-tomcat6] appears to have started a
thread named [Thread-0 (group:HornetQ-client-factory-threads-1831192424-1080990297)] but
has failed to stop it. This is very likely to create a memory leak.
{code}
There is lot of such logs, just the _Thread-counter_ is changing.
* 11 such logs just with showcase deploying and then right after undeploying
* bit more when after deploying playing a little bit with {{r:push}}
IMHO it is not just warning. I am experiencing {{Out of Memory}} issues when testing on
Tomcat. I need to use quite big {{Perm Gen}} and {{Heap size}}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)