ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31165] New: - should we set networkaddress.cache.ttl to something sensible in our startup scripts
Date Fri, 10 Sep 2004 14:49:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31165

should we set networkaddress.cache.ttl to something sensible in our startup scripts

           Summary: should we set networkaddress.cache.ttl to something
                    sensible in our startup scripts
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Wrapper scripts
        AssignedTo: dev@ant.apache.org
        ReportedBy: stevel@apache.org


by default java caches ns lookup values indefinitely, which is no good for long
lived builds (e.g. gridant) or things launched inside ant's own jvm with a long
lifespan. 

if we set the system property networkaddress.cache.ttl to something other than
-1 then java would reload at the frequency we say. For security reasons you
cannot do this inside the jvm itself, it has to be in wrapper/launcher code. 

Alternatively, we just document this next to the forthcoming <nslookup> task.

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


Mime
View raw message