[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642386#comment-14642386
]
Christofer Dutz commented on FLEX-34648:
----------------------------------------
I started writing some Integration Tests ... in one of them I set the timeout
to 1000 ms = 1 second and created 100 clients programaticaly. Then I waited for
two seconds and re-checked. BlazeDS did correctly close the clients. At least
the client list was empty. If the objects aren't cleaned up by the GC, probably
there are still strong referenced to them from somewhere. Do you have an idea
at to what might still be holding a strong reference?
> [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)
