Brian Baynes created GEODE-3698:
-----------------------------------
Summary: New protocol EOF exception on client disconnect
Key: GEODE-3698
URL: https://issues.apache.org/jira/browse/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 messages.
[fine 2017/09/19 11:06:22.469 PDT s1 <ServerConnection on port 40404 Thread 0>
tid=0x4c] Encountered EOF while processing message: {}
java.io.EOFException: Tried to deserialize protobuf message at EOF
at
org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.processOneMessage(ProtobufStreamProcessor.java:84)
at
org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.receiveMessage(ProtobufStreamProcessor.java:71)
at
org.apache.geode.internal.cache.tier.sockets.GenericProtocolServerConnection.doOneMessage(GenericProtocolServerConnection.java:78)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:557)
at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
