Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D94F3200CD2 for ; Wed, 12 Jul 2017 21:14:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D7E3416A5F5; Wed, 12 Jul 2017 19:14:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2E60316A5EF for ; Wed, 12 Jul 2017 21:14:03 +0200 (CEST) Received: (qmail 34839 invoked by uid 500); 12 Jul 2017 19:14:01 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 34824 invoked by uid 99); 12 Jul 2017 19:14:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2017 19:14:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 91747196249 for ; Wed, 12 Jul 2017 19:14:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id P7eFzlfivaaO for ; Wed, 12 Jul 2017 19:13:58 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0082A62750 for ; Wed, 12 Jul 2017 19:07:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 93459E0D34 for ; Wed, 12 Jul 2017 19:07:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4893B246EA for ; Wed, 12 Jul 2017 19:07:00 +0000 (UTC) Date: Wed, 12 Jul 2017 19:07:00 +0000 (UTC) From: "Galen O'Sullivan (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-3170) Geode keeps logging org.apache.geode.protocol.exception.InvalidProtocolMessageException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 12 Jul 2017 19:14:04 -0000 [ https://issues.apache.org/jira/browse/GEODE-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084514#comment-16084514 ] Galen O'Sullivan commented on GEODE-3170: ----------------------------------------- This issue is caused by a socket that's closed on the client side, which causes a SocketException to be thrown in ProtobufProtocolSerializer.deserialize . This throws a InvalidProtocolMessageException wrapping the SocketException (as an IOException), which is then rethrown as an IOException (whew!). We need to implement shutdown properly to have the shutdown method to call when the socket is no longer readable. I think it's reasonable to close a socket if we ever get an IOException from it. Are there other cases of IOException I'm missing? > Geode keeps logging org.apache.geode.protocol.exception.InvalidProtocolMessageException > --------------------------------------------------------------------------------------- > > Key: GEODE-3170 > URL: https://issues.apache.org/jira/browse/GEODE-3170 > Project: Geode > Issue Type: Bug > Components: client/server > Reporter: Alexander Murmann > Assignee: Galen O'Sullivan > Fix For: 1.3.0 > > Attachments: Proto-parse-error (1).txt > > > We've been seeing the logs getting filled up with exceptions if the new binary protocol is enabled. This quickly fills up the hard drive. > See attached file for example log -- This message was sent by Atlassian JIRA (v6.4.14#64029)