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? -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
