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
Bernd Fondermann wrote:
mmhh. I am religiously against religion in programming, too. ;-)
Earlier you proposed to get rid of abstract discussions like POJO vs.
Avalon. At least, please don't put me in a corner. This is only for
discussion.
Sorry Bernd, I didn't want to put you in a corner :-)
On 4/25/06, Stefano Bagnara [EMAIL PROTECTED] wrote:
AFAIK dnsjava should use weakreferences for its cache. So your
OutOfMemory should not be related to dnsjava itself.
The YourKit memory snapshots do not include weak and soft references
(unless you do something special when you started the
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
I didn't want to follow up on the thread about interfaces vs. reflection.
I want to critically look at the statement
if (obj instanceof Disposable) (Disposable) obj).dispose();
which is being used not in the container but inside server objects.
This strikes me as odd since IMO the interface
Alan D. Cabrera wrote:
I want to critically look at the statement
if (obj instanceof Disposable) (Disposable) obj).dispose();
More frequently you will find ContainerUtil.dispose(obj) that is the
same thing, but cleaner to read and simplify code browsability.
which is being used not in the
