From: Enrico F. <enr...@re...> - 2002-11-12 08:46:11
|
Thank you for your response. I=92m using 1.3.0 version.=20 I think that the problem is due to the high number of different domain in a very short time. So, the rate of new domain is greater than the rate of domain removed from the cache. I haven=92t seen all the dnsJava code jet, but I think that probably, a max number of domain to be cached need to be introduced so that the max amount of memory used by the application can be predetermined. Do you think I=92m right? In the next day, in my spare time, I=92ll try to better investigate the problem. =20 Enrico =20 -----Messaggio originale----- Da: dns...@li... [mailto:dns...@li...] Per conto di Brian Wellington Inviato: luned=EC 11 novembre 2002 21.57 A: Enrico Fustinoni Cc: dns...@li... Oggetto: Re: java.lang.outOfMemoryError On Mon, 11 Nov 2002, Enrico Fustinoni wrote: > Once again, I renew my compliments for dnsJava and hits improvements.=20 > I'm performing some test, so I wrote e program that finds the=20 > authoritative name server for a set of domains. After 45108 DNS query=20 > on different domains in about 4.5 hours the program stop with a=20 > java.lang.outOfMemoryError. I started the java virtual machine with=20 > java -Xmx100000000 -Xss10000000. >=20 > After looking the code, I think that this problem is due to an=20 > excessive use of memory from the cache class. What version of dnsjava? 1.3.0 uses a lot less memory than 1.2.4, and is=20 better about removing expired data. > Is this possible? Is there anything I can do to solve this problem? If you're using 1.2.4, upgrade. If you're using 1.3.0, I'm not really=20 sure. Brian ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ dnsjava-users mailing list dns...@li... https://lists.sourceforge.net/lists/listinfo/dnsjava-users |