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 2006/11/06 16:56:40 UTC
[jira] Resolved: (JAMES-674) DNSJava cache not properly handled
when using multiple dnsjava components
[ http://issues.apache.org/jira/browse/JAMES-674?page=all ]
Stefano Bagnara resolved JAMES-674.
-----------------------------------
Resolution: Fixed
Removed any static access to the dnsjava services: now we always use a "new Lookup" dynamically injecting the local cache and resolvers.
> DNSJava cache not properly handled when using multiple dnsjava components
> -------------------------------------------------------------------------
>
> Key: JAMES-674
> URL: http://issues.apache.org/jira/browse/JAMES-674
> Project: James
> Issue Type: Bug
> Affects Versions: Next Minor, Next Major
> Reporter: Stefano Bagnara
> Assigned To: Stefano Bagnara
> Fix For: Next Major
>
>
> Scenario:
> 2 dnsserver components: one have a bigger cachesize because it is used for an high traffic service, while the other has a small cache size because it is only used for intranet connections.
> I never made connections to the "low traffic" server, but its cache is filled up anyway. It is probably something related to the use of static xbill methods inside dnsServer.
--
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