[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611852#comment-14611852
]
[email protected] edited comment on FLEX-34648 at 7/2/15 12:04 PM:
--------------------------------------------------------------------------
Dears,
I have the same issue as mentioned by Mohamed Amer "The memory leak described
while using the "AMFEndpoint" which extends a BasePollingHTTPEndpoint not the
streaming endpoint."
I hope that we can have a solution soon as this is really impact our
application.
Thanks.
was (Author: [email protected]):
Dear Robert,
I have the same issue as mentioned by Mohamed Amer "The memory leak described
while using the "AMFEndpoint" which extends a BasePollingHTTPEndpoint not the
streaming endpoint."
I hope that we can have a solution soon as this is really impact our
application.
Thanks.
> [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: [email protected]
> 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)
