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 "Robert Burrell Donkin (JIRA)" <se...@james.apache.org> on 2009/03/20 11:44:51 UTC
[jira] Created: (JAMES-897) Identify Handler in Streamdump
Identify Handler in Streamdump
------------------------------
Key: JAMES-897
URL: https://issues.apache.org/jira/browse/JAMES-897
Project: JAMES Server
Issue Type: Sub-task
Components: James Core
Affects Versions: 3.0
Reporter: Robert Burrell Donkin
Assignee: Robert Burrell Donkin
Fix For: 3.0
Streamdump forks the input and output streams to file. This is a very useful feature when analysing the behaviour of a protocol. Unfortunately, the name gives no clue as to the identity of the handler which processes the input. This makes is hard to tie the logs in with the output.
The name of the streamdump should include identification information about the handler
--
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] Closed: (JAMES-897) Identify Handler in Streamdump
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/JAMES-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin closed JAMES-897.
---------------------------------------
Resolution: Fixed
> Identify Handler in Streamdump
> ------------------------------
>
> Key: JAMES-897
> URL: https://issues.apache.org/jira/browse/JAMES-897
> Project: JAMES Server
> Issue Type: Sub-task
> Components: James Core
> Affects Versions: 3.0
> Reporter: Robert Burrell Donkin
> Assignee: Robert Burrell Donkin
> Fix For: 3.0
>
>
> Streamdump forks the input and output streams to file. This is a very useful feature when analysing the behaviour of a protocol. Unfortunately, the name gives no clue as to the identity of the handler which processes the input. This makes is hard to tie the logs in with the output.
> The name of the streamdump should include identification information about the handler
--
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