[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=12814612#comment-12814612 ] 

Pavol Pitonak edited comment on RF-13250 at 10/16/13 9:43 AM:
--------------------------------------------------------------

Hi [~MilovdZee],
do you have org.richfaces.push.session.maxInactiveInterval and org.atmosphere.cpr.CometSupport.maxInactiveActivity context parameters set in your web.xml?

I saw OOME in my use-case but it failed because it couldn't create new native thread which isn't a problem described in this issue, is it? Am I correct that your application fills the whole heap?

How long does it take to get OOME? I.e. how fast will you get to the point of "extreme memory usage"?
                
      was (Author: ppitonak):
    Hi [~MilovdZee],
do you have org.richfaces.push.session.maxInactiveInterval and org.atmosphere.cpr.CometSupport.maxInactiveActivity context parameters set in your web.xml?

I saw OOME in my use-case but it failed because it couldn't create new native thread which isn't a problem described in this issue, is it? Am I correct that your application fills the whole heap?
                  
> 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