[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641966#comment-14641966
]
Christofer Dutz commented on FLEX-34648:
----------------------------------------
Hi Srinath,
thanks for that ... it will definitely help sorting this out. Reading through
your documentation. I too am a little concerned about simply making the VM drop
messages. What do you think about extending the Message type with a field that
specifies if we need the message to be delivered ... sort of like the
time-to-live property. But I'll discuss that on the dev-list ... eventually
someone else has another Idea and I'll like to hear those first.
I'll definitely work on this in the comming week as I would like to get a
version with this issue fixed out as soon as possible, as I'm having similar
trouble in one of my customers projects.
Chris
> [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)
