[
https://issues.apache.org/jira/browse/GEODE-9008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303525#comment-17303525
]
ASF subversion and git services commented on GEODE-9008:
--------------------------------------------------------
Commit 5b5f0a4b8ff1c5db3faf115f3d41bf8f300c034a in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5b5f0a4 ]
GEODE-9008: associate tid with connection when parsing message about (#758)
- This association wasn't happening if the connection on this thread
hadn't already sent a message. When that happened, we'd drop the
trace with the message body and mess up the state machine.
> gnmsg isn't parsing correctly if the first message on a thread is from the
> server
> ----------------------------------------------------------------------------------
>
> Key: GEODE-9008
> URL: https://issues.apache.org/jira/browse/GEODE-9008
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
>
> There's a dictionary mapping thread id --> connection, and it is only being
> populated on a client-to-server message. Thus, if the first message on a
> thread in a log file is server-to-client, there will be no dictionary entry
> for the connection, and the gnmsg state machine breaks. We need to add the
> tid entry in the dictionary for the connection when we hit a trace line for
> receipt of a header from the server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
