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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/10/12 20:03:33 UTC

[jira] Resolved: (JAMES-645) Instrumentation / Manageability for DNSServer / dnsjava

     [ https://issues.apache.org/jira/browse/JAMES-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Norman Maurer resolved JAMES-645.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Trunk)
                   3.0-M1
         Assignee: Norman Maurer

You can now do this via JMX ..

> Instrumentation / Manageability for DNSServer / dnsjava
> -------------------------------------------------------
>
>                 Key: JAMES-645
>                 URL: https://issues.apache.org/jira/browse/JAMES-645
>             Project: JAMES Server
>          Issue Type: Improvement
>          Components: DNSServer
>            Reporter: Stefano Bagnara
>            Assignee: Norman Maurer
>            Priority: Minor
>             Fix For: 3.0-M1
>
>
> It would be cool to add the needed code to be able to manage and monitor our dnsserver behaviours/caches.
> To know how much memory is used by the different caches could really help understanding what are the memory requirement for it.
> I don't know if a cache hit statistic is available in dnsjava, but this would help even more in tuning the size parameters.
> We are going to add many dns intensive checks by default (spf, black/white list, fastfail ehlo/domain checks) so this issue will become probably much important in the future.

-- 
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