[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655178#comment-14655178
]
Ahmed M Farghali commented on FLEX-34648:
-----------------------------------------
Christofer,
I have tried to generate this case in development environment, but the GC
always do the job, and also I found in the heap dumb a big consumption of
Objects ActiveMQMessageConsumer not AsyncMessage, which I guess means The
client didn't process the message(?). Can you share with us the Flex client
sample u used, and do you kill the flash player, through killing the browser
process?!
> [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)
