[
https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s...
]
Milo van der Zee commented on RF-13250:
---------------------------------------
Hello,
Neither of those parameters are set in my web.xml.
I do see that I get spikes in the threadcount but that does not seem to block the system.
Normally around 280 live threads with spikes to 3100. The problem in indeed in the
OOME's.
Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final
--------------------------------------------------------------
Key: RF-13250
URL:
https://issues.jboss.org/browse/RF-13250
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.4
Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14,
RichFaces 4.3.4, APR 1.4.5
Reporter: Milo van der Zee
Assignee: Pavol Pitonak
Labels: memoryleak
Hello,
I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash
with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the
problem is gone.
I also started seeing this message lot's of times:
{{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}}
I don't know if that has anything to do with the error. I set
{{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But
still the application went out-of-memory.
In the crashed system heap dump I see a lot of:
- AtomicBoolean (751.000, 15.0MB)
- ConcurrentLinkedQueue
- AtmospereRequest$Builder (60.042, 13.8MB)
To me it looks like it has something to do with Atmosphere. Any ideas?
Thanks,
Milo van der Zee
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira