[richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final

[Pavol Pitonak (JIRA)]

    [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12814047#comment-12814047 ] 

Pavol Pitonak commented on RF-13250:
------------------------------------

Hi, I created a simple web app simply increasing a counter and sending it to clients, I tried 1 Firefox and 11 Chrome clients concurrently and there was no sign of coming OOME. I also noticed a lot of AtomicBoolean and ConcurrentLinkedQueue instances but they were GC-ed  regularly so it doesn't seem to be problem.

There are configurations I tried:
# RichFaces 4.3.3.Final, Tomcat 7.0.42, Mojarra 2.1.19, OpenJDK 7
# RichFaces 4.3.4.Final, Tomcat 7.0.42, Mojarra 2.1.19, OpenJDK 7
# RichFaces 4.3.4.Final, Tomcat 7.0.39, Mojarra 2.1.19, OpenJDK 7
# RichFaces 4.3.4.Final, Tomcat 7.0.39, MyFaces 2.1.12, OpenJDK 7
# RichFaces 4.3.4.Final, Tomcat 7.0.39, MyFaces 2.1.12, Oracle JDK 7
# RichFaces 4.3.4.Final, Tomcat 7.0.39, MyFaces 2.1.12, Oracle JDK 6

Could you please write me which JDK are you using and how many concurrent clients does your application have?
                
> 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