[jboss-jira] [JBoss JIRA] Commented: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours
[ http://jira.jboss.com/jira/browse/JGRP-33?page=comments#action_12348148 ]
Bela Ban commented on JGRP-33:
------------------------------
Tony: please use the mailing lists to discuss issue such as these. JIRA should just be
used to create issues. If you have a use case (with code) that describes how to get an
OOM, that would help. You can turn local messages off through
Channel.setOpt(Channel.LOCAL, Boolean.FALSE);
JGroups throws OutOfMemoryError after running for a few hours
-------------------------------------------------------------
Key: JGRP-33
URL: http://jira.jboss.com/jira/browse/JGRP-33
Project: JGroups
Issue Type: Bug
Affects Versions: 2.2.8
Environment: SUN JDK 1.4.2_05 & SUN JDK 1.5.0 on Windows & Unix
platforms
Reporter: B.S.Navin
Assigned To: Bela Ban
Fix For: 2.2.8
Attachments: fc-fast-udp-tcpping.xml, fc-fast-udp.xml, JGroupsMemTest.java,
PublishThread2.java, runj10.sh
I ran 10 instances of a simple program with 3 threads. The max memory is kept as the JVM
default (64M). The 10 programs join the same JGroup and the threads in the programs keep
publishing a small hashmap at 5 second intervals.
The heap memory consumed (Runtime.totalMemory() - Runtime.freeMemory()) slowly increases
over a period of 4-5 hours and reaches the default max limit (64M) when it starts throwing
OutOfMemory errors on all instances.
I have run the program on unix and windows machines with 1G RAM.
Not able to make much from an HProf output of one of the instances.
This seems to be the cause for the JBossCache bug
"http://jira.jboss.com/jira/browse/JBCACHE-31" too.
I have tried out a UDP/PING and a UDP/TCPPING combination and this problem occurs in both
cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira