flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34648) [BLAZEDS]Memory Leak occurred in AsyncMessage when sending alot of
Date Wed, 05 Aug 2015 12:11:04 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655260#comment-14655260

Christofer Dutz commented on FLEX-34648:

Ok ... so I just comitted my sample application to the "4.8.0" branch of the BlazeDS repo.
But I would suggest to only use that branch for the example as I already did some fixing in
that branch. The project is located in the "examples/messaging-stresstest" directory (Be carefull
... I completely cleaned up the structure of the project ... moved all the old stuff to the
"attic" directory and changed the directory structures to be real-maven).

There was another issue I found as I managed to get the MessageClients and FlexClients invalidated,
there were still queues containing messages. So now as soon as a FlexClient is invalidated,
after invalidating the MessageClients, if flusches the content of the queues. After these
changes I could no longer observe the issues I was observing before.

> [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.shawky@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

View raw message