[ 
http://issues.apache.org/jira/browse/JAMES-679?page=comments#action_12449023 ] 
            
Noel J. Bergman commented on JAMES-679:
---------------------------------------

I would agree with backporting

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

to v2.3.x/minor-next.   Any reference to "-Dsun.net.inetaddr.ttl=10" should be 
eliminated, however.  That has already been deprecated by Sun and is 
non-standard.

> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to