You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Johan Stuyts (JIRA)" <ji...@apache.org> on 2008/06/03 20:38:45 UTC
[jira] Updated: (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 ]
Johan Stuyts updated THRIFT-12:
-------------------------------
Attachment: LoggingInsteadOfStandardIO.patch
This patch makes error messages go to a JDK logger instead of standard out for the following classes:
* {{TSimpleServer}}
* {{TThreadPoolServer}}
* {{TServerSocket}}
* {{TIOStreamTransport}}
* {{TSocket}}
Please review the log level and/or the messages used in the log statements.
> 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.