[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

2005-04-07 Thread Bela Ban (JIRA)
 [ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]

Bela Ban updated JGRP-33:
-

Priority: Major  (was: Critical)

downgraded to major; probably due to incorrect use of JGroups

 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
  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] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

2005-02-08 Thread B.S.Navin (JIRA)
 [ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]

B.S.Navin updated JGRP-33:
--

Environment: SUN JDK 1.4.2_05  SUN JDK 1.5.0 on Windows  Unix platforms  
(was: SUN JDK 1.4.2_05)

Was able to reproduce the issue using SUN JDK 1.5.0 too

 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] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

2005-02-07 Thread B.S.Navin (JIRA)
 [ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]

B.S.Navin updated JGRP-33:
--

Attachment: PublishThread2.java
JGroupsMemTest.java
runj10.sh

The sample programs  execution script for the reproducing the issue

 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
  Attachments: 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
-
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


[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

2005-02-07 Thread B.S.Navin (JIRA)
 [ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]

B.S.Navin updated JGRP-33:
--

Attachment: fc-fast-udp.xml
fc-fast-udp-tcpping.xml

Configuration files used for UDP/PING  UDP/TCPPING

 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
  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



---
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


[JBoss-dev] [JBoss JIRA] Updated: (JGRP-33) JGroups throws OutOfMemoryError after running for a few hours

2005-02-07 Thread Bela Ban (JIRA)
 [ http://jira.jboss.com/jira/browse/JGRP-33?page=history ]

Bela Ban updated JGRP-33:
-

Fix Version: 2.2.8

 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
  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



---
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