Mailing-List: contact issues-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Date: Thu, 11 Jun 2015 13:01:01 +0000 (UTC)
From: "Christofer Dutz (JIRA)" <jira@apache.org>
To: issues@flex.apache.org
Message-ID: <JIRA.12758045.1417028321000.45615.1434027661206@Atlassian.JIRA>
In-Reply-To: <JIRA.12758045.1417028321000@Atlassian.JIRA>
References: <JIRA.12758045.1417028321000@Atlassian.JIRA>
 <JIRA.12758045.1417028321589@arcas>
Subject: [jira] [Assigned] (FLEX-34648) [BLAZEDS]Memory Leak occurred in
 AsyncMessage when sending alot of
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christofer Dutz reassigned FLEX-34648:
--------------------------------------

    Assignee: Christofer Dutz

> [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)