You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Stefano Bagnara (JIRA)" <se...@james.apache.org> on 2007/02/04 17:41:05 UTC
[jira] Created: (JAMES-774) Add documentation for the dns ttl issue
Add documentation for the dns ttl issue
---------------------------------------
Key: JAMES-774
URL: https://issues.apache.org/jira/browse/JAMES-774
Project: James
Issue Type: Task
Affects Versions: 2.3.1-dev, Next Major
Reporter: Stefano Bagnara
Assigned To: Danny Angus
Add documentation to the site and/or to the config.xml about the unbounded cache issue in the JVM and how we introduced a system property networkaddress.cache.ttl that is read by phoenix at startup and used to override the java 1.4 Security.setProperty("networkaddress.cache.ttl" value.
By default in run.bat, phoenix.sh and james-server.sh (this one only in trunk) and wrapper.conf we added 300 seconds (-Dnetworkaddress.cache.ttl=300).
The cache is about positive results from dns lookups.
-1 means that the cache is never expired
0 means no cache
x>0 mean the number of seconds before expiration.
Please not that james trunk should not be affected by this cache because every usage of the InetAddress lookups have been removed by core code, but third party mailets could be afftected anyway, and this is why we added the property. James 2.3 instead still uses some InetAddress lookup and this property will save from OOM due to the unbounded cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [jira] Resolved: (JAMES-774) Add documentation for the dns ttl
issue
Posted by Stefano Bagnara <ap...@bago.org>.
Danny Angus (JIRA) ha scritto:
> *Sun* JVM DNS Lookup Configuration.
> <p>*Sun*'s JVM Internet address lookup uses a cache which is unbounded and doesn't time out.<br/>
> [...]
> <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>
AFAIK James probably does not work on non-Sun JVM (at least SSL support
may have big problems). That said I think that the "InetAddress"
unbounded cache behaviour is in the Java Language Specification so any
Java compliant JVM+ClassPath will probably exibit the same behaviour.
But I'm not an expert in this. Noel?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (JAMES-774) Add documentation for the dns ttl
issue
Posted by "Danny Angus (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Danny Angus resolved JAMES-774.
-------------------------------
Resolution: Fixed
Fix Version/s: Trunk
Added docs to trunk & 2.3 branch dns_configuration xdoc and to project FAQ xdoc. as below
Sun 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>
<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>
<p>For more on this read defect report <a href="http://issues.apache.org/jira/browse/JAMES-592">JAMES-592</a> and related defects.</p>
> Add documentation for the dns ttl issue
> ---------------------------------------
>
> Key: JAMES-774
> URL: https://issues.apache.org/jira/browse/JAMES-774
> Project: James
> Issue Type: Task
> Affects Versions: 2.3.1-dev, Next Major
> Reporter: Stefano Bagnara
> Assigned To: Danny Angus
> Fix For: 2.3.1-dev, Trunk
>
>
> Add documentation to the site and/or to the config.xml about the unbounded cache issue in the JVM and how we introduced a system property networkaddress.cache.ttl that is read by phoenix at startup and used to override the java 1.4 Security.setProperty("networkaddress.cache.ttl" value.
> By default in run.bat, phoenix.sh and james-server.sh (this one only in trunk) and wrapper.conf we added 300 seconds (-Dnetworkaddress.cache.ttl=300).
> The cache is about positive results from dns lookups.
> -1 means that the cache is never expired
> 0 means no cache
> x>0 mean the number of seconds before expiration.
> Please not that james trunk should not be affected by this cache because every usage of the InetAddress lookups have been removed by core code, but third party mailets could be afftected anyway, and this is why we added the property. James 2.3 instead still uses some InetAddress lookup and this property will save from OOM due to the unbounded cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-774) Add documentation for the dns ttl issue
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefano Bagnara updated JAMES-774:
----------------------------------
Fix Version/s: 2.3.1-dev
Updated fix version to make sure we remeber this in the 2.3.1 roadmap.
> Add documentation for the dns ttl issue
> ---------------------------------------
>
> Key: JAMES-774
> URL: https://issues.apache.org/jira/browse/JAMES-774
> Project: James
> Issue Type: Task
> Affects Versions: 2.3.1-dev, Next Major
> Reporter: Stefano Bagnara
> Assigned To: Danny Angus
> Fix For: 2.3.1-dev
>
>
> Add documentation to the site and/or to the config.xml about the unbounded cache issue in the JVM and how we introduced a system property networkaddress.cache.ttl that is read by phoenix at startup and used to override the java 1.4 Security.setProperty("networkaddress.cache.ttl" value.
> By default in run.bat, phoenix.sh and james-server.sh (this one only in trunk) and wrapper.conf we added 300 seconds (-Dnetworkaddress.cache.ttl=300).
> The cache is about positive results from dns lookups.
> -1 means that the cache is never expired
> 0 means no cache
> x>0 mean the number of seconds before expiration.
> Please not that james trunk should not be affected by this cache because every usage of the InetAddress lookups have been removed by core code, but third party mailets could be afftected anyway, and this is why we added the property. James 2.3 instead still uses some InetAddress lookup and this property will save from OOM due to the unbounded cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (JAMES-774) Add documentation for the dns ttl issue
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer updated JAMES-774:
--------------------------------
Fix Version/s: (was: 2.3.1)
(was: Trunk)
3.0-M1
> Add documentation for the dns ttl issue
> ---------------------------------------
>
> Key: JAMES-774
> URL: https://issues.apache.org/jira/browse/JAMES-774
> Project: JAMES Server
> Issue Type: Task
> Affects Versions: 2.3.1, 3.0
> Reporter: Stefano Bagnara
> Assignee: Danny Angus
> Fix For: 3.0-M1
>
>
> Add documentation to the site and/or to the config.xml about the unbounded cache issue in the JVM and how we introduced a system property networkaddress.cache.ttl that is read by phoenix at startup and used to override the java 1.4 Security.setProperty("networkaddress.cache.ttl" value.
> By default in run.bat, phoenix.sh and james-server.sh (this one only in trunk) and wrapper.conf we added 300 seconds (-Dnetworkaddress.cache.ttl=300).
> The cache is about positive results from dns lookups.
> -1 means that the cache is never expired
> 0 means no cache
> x>0 mean the number of seconds before expiration.
> Please not that james trunk should not be affected by this cache because every usage of the InetAddress lookups have been removed by core code, but third party mailets could be afftected anyway, and this is why we added the property. James 2.3 instead still uses some InetAddress lookup and this property will save from OOM due to the unbounded cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (JAMES-774) Add documentation for the dns ttl
issue
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487757 ]
Norman Maurer commented on JAMES-774:
-------------------------------------
Danny, any timeframe on this ?
> Add documentation for the dns ttl issue
> ---------------------------------------
>
> Key: JAMES-774
> URL: https://issues.apache.org/jira/browse/JAMES-774
> Project: James
> Issue Type: Task
> Affects Versions: 2.3.1-dev, Next Major
> Reporter: Stefano Bagnara
> Assigned To: Danny Angus
> Fix For: 2.3.1-dev
>
>
> Add documentation to the site and/or to the config.xml about the unbounded cache issue in the JVM and how we introduced a system property networkaddress.cache.ttl that is read by phoenix at startup and used to override the java 1.4 Security.setProperty("networkaddress.cache.ttl" value.
> By default in run.bat, phoenix.sh and james-server.sh (this one only in trunk) and wrapper.conf we added 300 seconds (-Dnetworkaddress.cache.ttl=300).
> The cache is about positive results from dns lookups.
> -1 means that the cache is never expired
> 0 means no cache
> x>0 mean the number of seconds before expiration.
> Please not that james trunk should not be affected by this cache because every usage of the InetAddress lookups have been removed by core code, but third party mailets could be afftected anyway, and this is why we added the property. James 2.3 instead still uses some InetAddress lookup and this property will save from OOM due to the unbounded cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org