Author: bago
Date: Tue Apr 17 14:43:39 2007
New Revision: 529780

URL: http://svn.apache.org/viewvc?view=rev&rev=529780
Log:
Fix xml syntax error from last FAQ entry.

Modified:
    james/project/trunk/server/src/site/xdoc/FAQ.xml

Modified: james/project/trunk/server/src/site/xdoc/FAQ.xml
URL: 
http://svn.apache.org/viewvc/james/project/trunk/server/src/site/xdoc/FAQ.xml?view=diff&rev=529780&r1=529779&r2=529780
==============================================================================
--- james/project/trunk/server/src/site/xdoc/FAQ.xml (original)
+++ james/project/trunk/server/src/site/xdoc/FAQ.xml Tue Apr 17 14:43:39 2007
@@ -319,7 +319,7 @@
                 <a name="18"/>
                <subsection name="How can I control Sun's JVM DNS Lookup 
Configuration.">
 <p>Sun's JVM Internet address lookup uses a cache which is unbounded and 
doesn't time out.<br/>
-This is obviously not great for a long running process like a mail server so 
we have introduced a system property <strong>networkaddress.cache.ttl<strong> 
that is used by the distributed phoenix start-up scripts, at startup, to 
override the java 1.4 
<strong>Security.setProperty("networkaddress.cache.ttl")</strong>.<br/> By 
default this is set to <strong>300</strong> seconds.</p>
+This is obviously not great for a long running process like a mail server so 
we have introduced a system property <strong>networkaddress.cache.ttl</strong> 
that is used by the distributed phoenix start-up scripts, at startup, to 
override the java 1.4 
<strong>Security.setProperty("networkaddress.cache.ttl")</strong>.<br/> By 
default this is set to <strong>300</strong> seconds.</p>
 <p>This workaround will only be present if you use James as distributed. If 
you use James in any other container, including different versions of Phoenix, 
you will need to ensure that you make a similar configuration change to allow 
the internet address cache to perform acceptably.</p>
 <p>James 2.3 has this workaround and it requires it to operate acceptably. 
Future versions of James will continue to have the workaround in place but will 
*not* require it. This will provide continued support for any mailets which you 
may deploy from other sources which might continue to use Sun's InetAddress 
class for DNS resolution.</p>
 <p>We are not currently aware of the behaviour of this cache in other JVM 
implementations, nor of the effect, if any, which this change might have on 
them</p>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to