[
https://issues.apache.org/jira/browse/FLEX-34648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643320#comment-14643320
]
Christofer Dutz commented on FLEX-34648:
----------------------------------------
I did encounter a similar problem in a scenario where a server was producing an
insane amount of messages (Actually the server was firing CRUD events for each
Creation/Update/Delete of an entity on a server. While it was no problem during
testing in a first produktion-like run, all went fine. But as soon as someone
actually logged in to the client, the heap was almost instantly flooded. We too
noticed that even the ttl of a message wasn't actually respected and messages
were not cleaned up. Unfortunately the side-effect was that the list in the
browser was not useable cause the list updated its content about 1000 times per
minute, driving users nuts. So we gave up the push and reverted back to simple
pull and manual refresh. As the problem was no longer pressing and BlazeDS was
not yet Apache, I didn't continue working on this :-( ... but now I'll think of
a way to simulate clients.
> [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)
