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

[Marcel Šebek (JIRA)]

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

Marcel Šebek commented on RF-13250:
-----------------------------------

Well, I've done some more investigations on this issue. At least one way how to leak resources is to send a malformed atmosphere request to an application. For example, send GET to /__richfaces_push?X-Atmosphere-Transport=long-polling

Then, with each such request, you should observe "Committed error code 400" and one leaked org.atmosphere.cpr.Meteor instance (it is leaked, because it is referenced from Meteor.cache). The error is probably produced by PushHandlerFilter - check for session == null.

I think it is time to reopen the bug now. If you cannot reproduce it, now I think I should be able to find the missing piece of information.
                
> 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