You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "ibrahem.shawky@gmail.com (JIRA)" <ji...@apache.org> on 2014/11/26 20:05:12 UTC
[jira] [Updated] (FLEX-34648) [BLAZEDS]Memory Leak occurred in
AsyncMessage when sending alot of
[ https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ibrahem.shawky@gmail.com updated FLEX-34648:
--------------------------------------------
Component/s: BlazeDS
Description: 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 it occupied by AsyncMessage objects this is very clear from the generated heap dump.
Affects Version/s: BlazeDS 4.7
> [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
> 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 it occupied by AsyncMessage objects this is very clear from the generated heap dump.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)