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

["Mark Slee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602043#action_12602043 ] 

Mark Slee commented on THRIFT-12:
---------------------------------

This patch looks good to me. I also agree with David that java.util.logging is preferable here, as one of the main philosophies of Thrift is to be as lightweight and dependency-free as possible.

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