geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Baynes (JIRA)" <>
Subject [jira] [Created] (GEODE-3698) New protocol EOF exception on client disconnect
Date Mon, 25 Sep 2017 21:05:00 GMT
Brian Baynes created GEODE-3698:

             Summary: New protocol EOF exception on client disconnect
                 Key: GEODE-3698
             Project: Geode
          Issue Type: Bug
          Components: client/server
            Reporter: Brian Baynes

When a new protocol client closes the socket, looks like the server logs an EOF exception
on a null message.  Investigate ProtobufStreamProcessor and handling of client disconnects/null

[fine 2017/09/19 11:06:22.469 PDT s1 <ServerConnection on port 40404 Thread 0> tid=0x4c]
Encountered EOF while processing message: {} Tried to deserialize protobuf message at EOF
	at org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.processOneMessage(
	at org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.receiveMessage(
	at org.apache.geode.internal.cache.tier.sockets.GenericProtocolServerConnection.doOneMessage(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
	at org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$

This message was sent by Atlassian JIRA

View raw message