You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alexander Murmann (JIRA)" <ji...@apache.org> on 2017/07/07 15:57:00 UTC
[jira] [Commented] (GEODE-3170) Geode keeps logging
org.apache.geode.protocol.exception.InvalidProtocolMessageException
[ https://issues.apache.org/jira/browse/GEODE-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078285#comment-16078285 ]
Alexander Murmann commented on GEODE-3170:
------------------------------------------
Hitesh came up with the very likely theory that this is caused by `/gemfire/open/geode-core/src/main/java/org/apache/geode/internal/cache/tier/sockets/GenericProtocolServerConnection.java:61` taking messages off the socket in a while lop regardless of their being new messages or not.
> 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 queues
> Reporter: Alexander Murmann
> 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)