Menu
▾
▴
dnsjava-users
|
From: Brian W. <bwe...@xb...> - 2002-10-18 18:31:17
|
I released dnsjava 1.3.0. It's basically the same as the beta, with one
bug fix to the cache cleaner, a minor optimization to the cache, and the
Name.getLabel() function.
There are a bunch of optimizations to both speed and memory usage and a
number of bug fixes since 1.2.4. A lot of internal code was updated to
use Collections, so Java 1.2 or greater is now required. Large portions
of code have been completely rewritten (Name.java, for example), and the
new code is a lot more sane and has a cleaner API.
Changelog below.
Brian
--------
10/16/2002
- 1.3.0 released.
10/11/2002
- Add Name.getLabel()
10/10/2002
- When cleaning the cache, catch ConcurrentModificationExceptions.
10/8/2002
- Cleanups to Cache.addMessage() and the Credibility code.
10/7/2002
- Fix problems with search path handling in the dns class.
- Possible race condition fixes to the Cache code.
10/6/2002
- Fix minor bugs in Name code (Bob Halley <bob...@no...>)
10/1/2002
- Memory usage and speed improvements to the TypeMap class.
9/25/2002
- Add the verbosecache option.
- Significant memory usage improvements to the Name class.
9/23/2002
- Memory usage improvements to the ARecord class.
9/16/2002
- Support for NetWare's sys:/etc/resolv.cfg file.
(Scott Villinski <sc...@vi...>)
9/5/2002
- When looking for an rdataset in a zone or cache, seeing a CNAME
above the name is not an error.
(reported by Andrew Houghton <aa...@vo...>)
8/31/2002
- Changed the code that dynamically loads record types; hopefully
this will solve some of the mysterious problems that I think
are related to non-English versions of Windows.
- Clean up the Name code.
8/28/2002
- Remove support for bitstring labels, since they're now deprecated.
8/16/2002
- Address.isDottedQuad didn't check to see if the input String
contained characters after an IP address.
(Marcos Sanz <sa...@de...>)
8/11/2002
- Querying for a nonexistant name with exactly one label didn't return.
8/10/2002
- Add Ant build script (Blake Ramsdell <bl...@br...>)
8/6/2002
- The AAAARecord constructor was broken.
- The Record class now implements Comparable.
6/22/2002
- Significant speed improvements in the Record class and its
subclasses.
6/20/2002
- Add Zone.removeRecord() (based on code from Adam Cassar
<ada...@ne...>)
- Add Zone.toMasterFile() (based on code from Adam Cassar)
- Performance enhancements to the Name object.
- Add the "-t type" option to the lookup program.
6/16/2002
- Update lots of code to use Collections instead of JDK 1.1
Vectors & Hashtables.
5/28/2002
- fix some limitations of name parsing.
(reported by Tasos Kotsikonas <ta...@bo...>)
5/4/2002
- added the 'sleep' and 'date' commands to the update client.
(Olafur Gudmundsson <og...@og...>)
|
|
From: Brian W. <bwe...@xb...> - 2002-10-18 18:31:17
|
I released dnsjava 1.3.0. It's basically the same as the beta, with one
bug fix to the cache cleaner, a minor optimization to the cache, and the
Name.getLabel() function.
There are a bunch of optimizations to both speed and memory usage and a
number of bug fixes since 1.2.4. A lot of internal code was updated to
use Collections, so Java 1.2 or greater is now required. Large portions
of code have been completely rewritten (Name.java, for example), and the
new code is a lot more sane and has a cleaner API.
Changelog below.
Brian
--------
10/16/2002
- 1.3.0 released.
10/11/2002
- Add Name.getLabel()
10/10/2002
- When cleaning the cache, catch ConcurrentModificationExceptions.
10/8/2002
- Cleanups to Cache.addMessage() and the Credibility code.
10/7/2002
- Fix problems with search path handling in the dns class.
- Possible race condition fixes to the Cache code.
10/6/2002
- Fix minor bugs in Name code (Bob Halley <bob...@no...>)
10/1/2002
- Memory usage and speed improvements to the TypeMap class.
9/25/2002
- Add the verbosecache option.
- Significant memory usage improvements to the Name class.
9/23/2002
- Memory usage improvements to the ARecord class.
9/16/2002
- Support for NetWare's sys:/etc/resolv.cfg file.
(Scott Villinski <sc...@vi...>)
9/5/2002
- When looking for an rdataset in a zone or cache, seeing a CNAME
above the name is not an error.
(reported by Andrew Houghton <aa...@vo...>)
8/31/2002
- Changed the code that dynamically loads record types; hopefully
this will solve some of the mysterious problems that I think
are related to non-English versions of Windows.
- Clean up the Name code.
8/28/2002
- Remove support for bitstring labels, since they're now deprecated.
8/16/2002
- Address.isDottedQuad didn't check to see if the input String
contained characters after an IP address.
(Marcos Sanz <sa...@de...>)
8/11/2002
- Querying for a nonexistant name with exactly one label didn't return.
8/10/2002
- Add Ant build script (Blake Ramsdell <bl...@br...>)
8/6/2002
- The AAAARecord constructor was broken.
- The Record class now implements Comparable.
6/22/2002
- Significant speed improvements in the Record class and its
subclasses.
6/20/2002
- Add Zone.removeRecord() (based on code from Adam Cassar
<ada...@ne...>)
- Add Zone.toMasterFile() (based on code from Adam Cassar)
- Performance enhancements to the Name object.
- Add the "-t type" option to the lookup program.
6/16/2002
- Update lots of code to use Collections instead of JDK 1.1
Vectors & Hashtables.
5/28/2002
- fix some limitations of name parsing.
(reported by Tasos Kotsikonas <ta...@bo...>)
5/4/2002
- added the 'sleep' and 'date' commands to the update client.
(Olafur Gudmundsson <og...@og...>)
|
|
From: Enrico F. <enr...@re...> - 2002-11-11 15:54:34
|
Once again, I renew my compliments for dnsJava and hits improvements. I'm performing some test, so I wrote e program that finds the authoritative name server for a set of domains. After 45108 DNS query on different domains in about 4.5 hours the program stop with a java.lang.outOfMemoryError. I started the java virtual machine with java -Xmx100000000 -Xss10000000. After looking the code, I think that this problem is due to an excessive use of memory from the cache class. Is this possible? Is there anything I can do to solve this problem? Thanks for your interest. Enrico |
|
From: Brian W. <bwe...@xb...> - 2002-11-11 20:57:08
|
On Mon, 11 Nov 2002, Enrico Fustinoni wrote: > Once again, I renew my compliments for dnsJava and hits improvements. > I'm performing some test, so I wrote e program that finds the > authoritative name server for a set of domains. > After 45108 DNS query on different domains in about 4.5 hours the > program stop with a java.lang.outOfMemoryError. > I started the java virtual machine with java -Xmx100000000 -Xss10000000. > > After looking the code, I think that this problem is due to an 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 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 sure. Brian |
|
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 |
|
From: Brian W. <bwe...@xb...> - 2002-11-12 19:31:46
|
On Tue, 12 Nov 2002, Enrico Fustinoni wrote: > 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? No, because the amount of memory per cached domain is not constant, so=20 limiting the cache based on the number of domains won't work as you'd=20 expect. The ultimate correct solution is to make the cache cleaner more=20 aggressive, and more likely to successfully clean the entire cache withou= t=20 getting an exception. This means that the cache would need a new data=20 structure. A good temporary solution would be to add a setMaxCache() function to the= =20 Cache object, like the setMaxNCache() function. Then you could set all=20 data to be cached for no more than, say, an hour, and the cache cleaner=20 would hopefully be able to remove more of it. In any case, I won't have time to touch dnsjava code at all for the next=20 few weeks. > In the next day, in my spare time, I=92ll try to better investigate the > problem. =20 OK. Brian |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X