Noel J. Bergman wrote:
A third, alternative, workaround is to add:
java.security.Security.setProperty("networkaddress.cache.ttl" , "10");
somewhere in our code.
<<sigh>> Except that it addresses none of the other technical flaws with using
Sun's code. If you think that this is such a good idea, why don't we do it throughout the
trunk code, too?
--- Noel
You are right, we probably should add this also to trunk.
In fact I think it should be probably part of the container: a container
that is built to run a long running application should make sure that
the dns cache is expired someway.
Furthermore, in trunk we already optimized the use of the caches and
their expiration by moving to dnsjava (even if this still needs some
tuning because it currenlty use a mix of static and standard calls) in
our sourcecode but it could happen (or maybe it already happen) that
some third party library we use still make use of InetAddress "flawed"
methods, and the above property would save us from the possible
OutOfMemory because of the unbounded cache.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
