[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642928#comment-14642928
]
Srinath H S commented on FLEX-34648:
------------------------------------
Hi chris,
To reproduce you will have to open consumers on flex side and do not close the
sessions in flex either, You need to break the polling, eg, kill the browser.
I was looking into the code where the timeout should invalidate, however the
session still remains in heap. Unfortunately we have not moved out of flex in
our application towards a REST service, when we had this problem the only way
to reproduce was to keep pushing lot of messages for a really long time (24hrs)
and we only had a handful of sessions open. I also remember there is a memory
leak on the flex side of messaging also and it slows down the browser
drastically and that in turn slows the polling process and messages gets piled
up.
> [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of
> -------------------------------------------------------------------
>
> Key: FLEX-34648
> URL: https://issues.apache.org/jira/browse/FLEX-34648
> Project: Apache Flex
> Issue Type: Bug
> Components: BlazeDS
> Affects Versions: BlazeDS 4.7
> Reporter: ibrahem.sha...@gmail.com
> Assignee: Christofer Dutz
> Priority: Critical
>
> a memory leak occurred when sending alot of AsyncMessage through BLAZEDS in a
> real time systems which is heavilly using messaging however we are increasing
> the jvm heap size to 4 GB 80% of the size is occupied by AsyncMessage
> objects this is very clear from the generated heap dump.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
