[jira] [Commented] (GEODE-3408) Flood of EOF warnings
[ https://issues.apache.org/jira/browse/GEODE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141884#comment-16141884 ] ASF subversion and git services commented on GEODE-3408: Commit 6eb8611d3f29ffc8514ac8bda5edc4e914c2e94d in geode's branch refs/heads/feature/GEODE-3503 from [~bschuchardt] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6eb8611 ] GEODE-3408 Flood of EOF warnings Modified the message handler to catch EOFException and effect shutdown of the connection & server thread. I also fixed the handling of IOException. The methods invoked are the same as for the old protocol's handling of EOFException and IOException > Flood of EOF warnings > - > > Key: GEODE-3408 > URL: https://issues.apache.org/jira/browse/GEODE-3408 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Augustus Lidaka > Fix For: 1.3.0 > > > Experimenting with the protobuf changes in the {{develop}} branch around > commit {{cea8312}}, after running a client scenario for a while I'm seeing a > flood of messages like the following. There appears to be one for each new > message sent from the client. > {code} > [warning 2017/08/07 11:15:16.628 PDT gbp-server 40404 Thread 9> tid=0x61] java.io.EOFException: Tried to deserialize protobuf > message at EOF > {code} > The log spam doesn't happen on initial connection and interaction, but for > example a loop like the following begins triggering it within 100 iterations > (possibly less): > {code} > for (var i = 0;; i++) > { > var region = ...; // connect to localhost, single-node server, get region > region.Put(i, i); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3408) Flood of EOF warnings
[ https://issues.apache.org/jira/browse/GEODE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140885#comment-16140885 ] ASF subversion and git services commented on GEODE-3408: Commit 6eb8611d3f29ffc8514ac8bda5edc4e914c2e94d in geode's branch refs/heads/develop from [~bschuchardt] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=6eb8611 ] GEODE-3408 Flood of EOF warnings Modified the message handler to catch EOFException and effect shutdown of the connection & server thread. I also fixed the handling of IOException. The methods invoked are the same as for the old protocol's handling of EOFException and IOException > Flood of EOF warnings > - > > Key: GEODE-3408 > URL: https://issues.apache.org/jira/browse/GEODE-3408 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Augustus Lidaka > > Experimenting with the protobuf changes in the {{develop}} branch around > commit {{cea8312}}, after running a client scenario for a while I'm seeing a > flood of messages like the following. There appears to be one for each new > message sent from the client. > {code} > [warning 2017/08/07 11:15:16.628 PDT gbp-server 40404 Thread 9> tid=0x61] java.io.EOFException: Tried to deserialize protobuf > message at EOF > {code} > The log spam doesn't happen on initial connection and interaction, but for > example a loop like the following begins triggering it within 100 iterations > (possibly less): > {code} > for (var i = 0;; i++) > { > var region = ...; // connect to localhost, single-node server, get region > region.Put(i, i); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3408) Flood of EOF warnings
[ https://issues.apache.org/jira/browse/GEODE-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118827#comment-16118827 ] Michael Martell commented on GEODE-3408: This may be related to the hitting the connection limit. See GEODE-3409. > Flood of EOF warnings > - > > Key: GEODE-3408 > URL: https://issues.apache.org/jira/browse/GEODE-3408 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Augustus Lidaka > > Experimenting with the protobuf changes in the {{develop}} branch around > commit {{cea8312}}, after running a client scenario for a while I'm seeing a > flood of messages like the following. There appears to be one for each new > message sent from the client. > {code} > [warning 2017/08/07 11:15:16.628 PDT gbp-server 40404 Thread 9> tid=0x61] java.io.EOFException: Tried to deserialize protobuf > message at EOF > {code} > The log spam doesn't happen on initial connection and interaction, but for > example a loop like the following begins triggering it within 100 iterations > (possibly less): > {code} > for (var i = 0;; i++) > { > var region = ...; // connect to localhost, single-node server, get region > region.Put(i, i); > } > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)