james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Fondermann (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-635) Make information about configured Processors, Mailets and Matchers available at runtime
Date Sun, 29 Oct 2006 13:45:17 GMT
     [ http://issues.apache.org/jira/browse/JAMES-635?page=all ]

Bernd Fondermann updated JAMES-635:

    Attachment: screenshot_jconsole.png

shows how this feature is looking like in JConsole

> Make information about configured Processors, Mailets and Matchers available at runtime
> ---------------------------------------------------------------------------------------
>                 Key: JAMES-635
>                 URL: http://issues.apache.org/jira/browse/JAMES-635
>             Project: James
>          Issue Type: New Feature
>          Components: SpoolManager & Processors, Remote Manager
>    Affects Versions: Trunk
>            Reporter: Bernd Fondermann
>         Assigned To: Bernd Fondermann
>         Attachments: screenshot_jconsole.png
> Add functionality to RemoteManager and JMX interface to show all Processors and related
Mailets and Matchers.
> (JAMES-123 is a similar issue, but more targeted towards reading the classpath, so I
am opening a new and fresh JIRA.)
> In the RM, the Processor names can be listed, and furthermore all Mailets and Matchers
for one Processor.
> In JMX, each Processor, Mailet and Matcher has its own MBean and they are naturally being
grouped by the JMX client in a tree representing the parent/child relationships between Processor
and Mailets/Matchers.
> Names and configuration parameters are shown in the basic version.
> Additionally, I would like to add live statistics about how many mails were processed
and to support JMX notifications for live problem analysis without restarting the server for
adding logger mailets or otherwisely interrupting the running server.
> Currently, I am not planning to make it possible to alter configuration parameters at
runtime or to re-wire the processing chain. This is postponed for future decision.

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

View raw message