In the dnsjava changelog I see this after the 1.6.2 release we bundle
with James 2.2.0:
4/3/2005 - Change the Cache from being periodically cleaned to being
size-bounded.
This change is part of dnsjava-2.0+. Maybe that james 2.3.0 will fix
this problem.
Otherwise you could try rebuilding James 2.2.0 with dnsjava2. I remember
I changed the DNSServer to do this upgrade but it should be an easy task.
Stefano
Serge Knystautas wrote:
On 4/25/06, Serge Knystautas <[EMAIL PROTECTED]> wrote:
Actually, it gets a bit worse. Out of my 52MB heap that is not
gc'able, here is what I see:
- 44MB in an xbill cache held by Lookup code that is held by an avalon
policy class holder.
- 3.2MB in an xbill cache held by DNS server
- 1.7MB in a cache behind java.net.InetAddress
So 49MB or 52MB heap that is not gc'able are from DNS cache entries. :)
Just to keep score, I did a snapshot now and had the following stats:
- 87.3MB total heap used
- 75.6MB DNS.Lookup via that policy class holder.
- 5.4MB DNS.Lookup via the James DNSServer
- 2.7MB via java.net.InetAddress
On the bright side is that non-DNS caches in James are still using
only a tiny amount of heap (3.6MB or about 1/25th of the total heap
space and 1% of what I had allocated).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
