You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Vijay (JIRA)" <ji...@apache.org> on 2011/07/29 06:34:09 UTC

[jira] [Created] (THRIFT-1246) Improve logging: Change TNonblockingServer internalRead to trace from warn

Improve logging: Change TNonblockingServer internalRead to trace from warn
--------------------------------------------------------------------------

                 Key: THRIFT-1246
                 URL: https://issues.apache.org/jira/browse/THRIFT-1246
             Project: Thrift
          Issue Type: Improvement
          Components: Java - Library
    Affects Versions: 0.7
         Environment: JVM
            Reporter: Vijay
             Fix For: 0.7


In the actual world we will have a lot of connection resets hence it will be better to log those messages as trace than logging as errors and warnings.
Or we can make this logging configurable. Let me know thanks!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (THRIFT-1246) Improve logging: Change TNonblockingServer internalRead to trace from warn

Posted by "Vijay (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vijay updated THRIFT-1246:
--------------------------

    Priority: Trivial  (was: Major)

> Improve logging: Change TNonblockingServer internalRead to trace from warn
> --------------------------------------------------------------------------
>
>                 Key: THRIFT-1246
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1246
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Java - Library
>    Affects Versions: 0.7
>         Environment: JVM
>            Reporter: Vijay
>            Priority: Trivial
>             Fix For: 0.7
>
>
> In the actual world we will have a lot of connection resets hence it will be better to log those messages as trace than logging as errors and warnings.
> Or we can make this logging configurable. Let me know thanks!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira