[
https://issues.apache.org/jira/browse/THRIFT-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James E. King III closed THRIFT-1246.
-------------------------------------
Resolution: Incomplete
Assignee: James E. King III
Fix Version/s: (was: 1.0)
This report is incomplete; the message(s) in question were not identified. I
agree with you that handling an unexpected client disconnect should not be a
warning or error. It happens all the time. Need more information on which
logging statements are involved. Feel free to reopen this and submit a pull
request if you have a fix.
> 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
> Assignee: James E. King III
> Priority: Trivial
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
