[
https://issues.apache.org/jira/browse/BOOKKEEPER-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744922#comment-13744922
]
Ivan Kelly commented on BOOKKEEPER-660:
---------------------------------------
Btw, info is the correct log level. A client going away without cleanly closing
the connection is a pretty regular occurrence, and not something that should
draw the attention of the admin, as a warn log would.
> Logs too noisy on NIOServerFactory when client drops a connection
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-660
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-660
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Ivan Kelly
> Assignee: Matteo Merli
> Priority: Minor
> Fix For: 4.2.2
>
> Attachments: BOOKKEEPER-660.diff
>
>
> When a client drops a connection, the server throws an exception. It should
> only log at info level and close the socket.
> {code}
> if (k.isReadable()) {
> int rc = sock.read(incomingBuffer);
> if (rc < 0) {
> throw new IOException("Read error");
> }
> if (incomingBuffer.remaining() == 0) {
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
