Hi Serge,
AFAIK dnsjava should use weakreferences for its cache. So your
OutOfMemory should not be related to dnsjava itself.
The dnsjava bundled with James 2.2.0 is rather old, but dnsjava2 is not
compatible with older versions.
Maybe that the dnsjava 1.x bundled with James 2.2.0 has memory leaks,
but I don't think so, because I used James 2.2.0 for long time with no
memory issues.
I don't know if dnsjava has tuning parameters or other ways to control
its caching.
Stefano
Serge Knystautas wrote:
Every now and then, James grinds to a halt (James 2.2.0, JDK 1.5.0_06,
linux). It ground to a halt this morning, and tests showed it had run
out of heap space (mx set to 256MB).
Unfortunately I couldn't get a snapshot then, but I took one this
evening... after running half a day, James was holding onto 52MB
already. I couldn't figure out what in James could use that much
heap. Guesses?... :)
Yes, the xbill DNS library had used up 44MB of heap space. Now, I use
a lot of spam blacklists, so that might be causing it, but it seems to
me to be a huge room for improving heap space. Is there anyway we can
cap this cache size or ideally send it to disk?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
