You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Woo Ju Shin (JIRA)" <ji...@apache.org> on 2015/12/27 05:40:50 UTC

[jira] [Issue Comment Deleted] (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 ]

Woo Ju Shin updated FLEX-34648:
-------------------------------
    Comment: was deleted

(was: I got this all wrong.
The new version of Apache-tomcat's configuration was different to the old one.
The declaration of PersistentManager was neglected.
After configuring Apache-tomcat 7.0.64's context.xml we don't get this problem anymore.)

> [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
(v6.3.4#6332)