You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "David Reiss (JIRA)" <ji...@apache.org> on 2008/06/30 23:00:46 UTC

[jira] Assigned: (THRIFT-12) TThreadPoolServer should log exceptions and events via log4j instead of to stdout

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

David Reiss reassigned THRIFT-12:
---------------------------------

    Assignee: Johan Stuyts  (was: David Reiss)

> TThreadPoolServer should log exceptions and events via log4j instead of to stdout
> ---------------------------------------------------------------------------------
>
>                 Key: THRIFT-12
>                 URL: https://issues.apache.org/jira/browse/THRIFT-12
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Library (Java)
>            Reporter: Bryan Duxbury
>            Assignee: Johan Stuyts
>            Priority: Minor
>         Attachments: LoggingInsteadOfStandardIO.patch
>
>
> It would be extremely useful if it was easier to control the error and event logging from the TThreadPoolServer. This would make debugging and management much easier. Log4j has a fair amount of momentum as a project - would there be any objection to bundling log4j and using that in the server?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.