james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman (JIRA)" <server-...@james.apache.org>
Subject [jira] Reopened: (JAMES-679) Make sure our container use an expiration for cached dns data
Date Sat, 11 Nov 2006 20:51:38 GMT
     [ http://issues.apache.org/jira/browse/JAMES-679?page=all ]

Noel J. Bergman reopened JAMES-679:

Please change this from 10 to 0, as in:

  java.security.Security.setProperty("networkaddress.cache.ttl" , "0");

The change you made doesn't necessarily do what you think it does because the code in Sun's
InetAddress.Cache implementation handles expiration only when the host name is queried or
another entry is put (at which point it loops through the entire cache looking for expired
entries).  Otherwise, it just takes up space.

For our purposes, it would be better to use the InetAddressCachePolicy.NEVER special case.

> Make sure our container use an expiration for cached dns data
> -------------------------------------------------------------
>                 Key: JAMES-679
>                 URL: http://issues.apache.org/jira/browse/JAMES-679
>             Project: James
>          Issue Type: Improvement
>    Affects Versions: 2.3.0
>            Reporter: Stefano Bagnara
>         Assigned To: Stefano Bagnara
>             Fix For: Next Major
> Noel J. Bergman wrote:
> > Stefano Bagnara wrote:
> >> 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.
> > 
> > Perhaps, but I would rather vet the code, and be more careful about what we use.
 Now that we know one of the things to look for carefully, we can avoid it.  The better solution
is to avoid the problem, not mask it.
> > 
> > 	--- Noel
> I agree: we avoid it in trunk because of this.
> About the "not masking" I think that even if we solved it we should better add the property
because our users could easily make our mistakes and use InetAddress in their mailets. The
fact that DNSServer is not part of the mailet apis incentivate them to use InetAdress and
not the James Server specific service.
> So I think we should really add the ttl property.
> Either "-Dsun.net.inetaddr.ttl=10" in the command line or 
> java.security.Security.setProperty("networkaddress.cache.ttl" , "10"); 
> Should work.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message