[jboss-jira] [JBoss JIRA] (JGRP-1638) Memory leak

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778924#comment-12778924 ] 

Bela Ban edited comment on JGRP-1638 at 6/3/13 12:20 PM:
---------------------------------------------------------

git bisect shows 434760c8eca1223bd3f911895cdc9c8109590946 as first bad commit. This sends STABLE messages by default to the coordinator instead of multicasting them to all members. Need to investigate what went wrong here.
WORKAROUND: set STABLE.send_stable_msgs_to_coord_only to false
                
      was (Author: belaban):
    git bisect shows 434760c8eca1223bd3f911895cdc9c8109590946 as first bad commit. This sends STABLE messages by default to the coordinator only instead of multicasting them to all members. Ned to investigate what went wrong here.
WORKAROUND: set STABLE.send_stable_msgs_to_coord_only to false
                  
> Memory leak
> -----------
>
>                 Key: JGRP-1638
>                 URL: https://issues.jboss.org/browse/JGRP-1638
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Critical
>             Fix For: 3.4
>
>
> Running MPerf with conf/fast-local.xml (2 members on the same host, 20 million messages each) creates a memory leak in 3.4.x.
> This runs perfectly 3.2.8.Final, so it must be something that was introduced in 3.3.x (3.4.x at this time has almost no diffs to 3.3.0.Final).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira