[JBoss-dev] [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_12315957 ] Bela Ban commented on JGRP-33: -- You either need to call receive() (and discard the msg), or set Channel.LOCAL to false. JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 SUN JDK 1.5.0 on Windows Unix platforms Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [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_12315958 ] B.S.Navin commented on JGRP-33: --- What does Channel.LOCAL do? I don't see any explanation in the java docs. JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 SUN JDK 1.5.0 on Windows Unix platforms Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [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_12315959 ] Bela Ban commented on JGRP-33: -- It discards all messages sent by myself. Let's not use JIRA for questions; let's use the jgroups dev list in the future JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 SUN JDK 1.5.0 on Windows Unix platforms Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [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_12315953 ] James Wilson commented on JGRP-33: -- I am not sure that the test case provided actually demonstrates the issue (if there is one). The test case continuously sends messages via a JChannel instance, but it never calls the receive method on the channel instance, so the queue of messages to be received will grow forever. While this definitely increases the size of the heap, I think that this is a misuse of JChannel, not a bug. JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 SUN JDK 1.5.0 on Windows Unix platforms Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [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_12315954 ] B.S.Navin commented on JGRP-33: --- But in many cases (and in this one too), there would be some members who just send messages to the group and are not concerned with receiving any of the messages. In such cases, the member would not call receive but will keep sending messages through the JChannel. Is there any other way for implementing such a case? JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 SUN JDK 1.5.0 on Windows Unix platforms Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical Fix For: 2.2.8 Attachments: JGroupsMemTest.java, PublishThread2.java, fc-fast-udp-tcpping.xml, fc-fast-udp.xml, 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [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_12315203 ] B.S.Navin commented on JGRP-33: --- Have tried reproduced this issue with the JGroups 2.2.7 release as well as the latest JGroups HEAD. JGroups throws OutOfMemoryError after running for a few hours - Key: JGRP-33 URL: http://jira.jboss.com/jira/browse/JGRP-33 Project: JGroups Type: Bug Versions: 2.2.8 Environment: SUN JDK 1.4.2_05 Reporter: B.S.Navin Assignee: Bela Ban Priority: Critical 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
