[
https://issues.apache.org/jira/browse/GEODE-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145730#comment-17145730
]
ASF subversion and git services commented on GEODE-8297:
--------------------------------------------------------
Commit e5a0b9a0ca9a35ef3c2cafde866af1705bc7a006 in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e5a0b9a ]
GEODE-8297: fix tcrmessage timeout (#623)
- Use correct initialization for TcrMessage::m_timeout
- Intent was to set it 15 seconds, but it was actually being set to 15ms
- Rename DEFAULT_TIMEOUT constants, remove units from name since they're no
longer relevant
> TcrMessage default timeout is set to 15ms, rather than 15 seconds
> -----------------------------------------------------------------
>
> Key: GEODE-8297
> URL: https://issues.apache.org/jira/browse/GEODE-8297
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
>
> While analyzing a log from a bug report, I noticed a trace message from
> TcrConnection::sendData:
> {quote}{{[debug <<deleted>> 123145454981120] before send len 99
> sendTimeoutSec = *15000us* checkConnected = 1 m_connected 1}}
> {quote}
>
> It appears, from further digging, that we are indeed using a 15ms timeout for
> (at least) the
> USER_CREDENTIAL_MESSAGE. This will happen for any message we don't
> explicitly set the timeout on before sending. Potentially this is a cause
> for a lot of random network timeout failures. Regardless of whether or not
> it's for sure causing problems, it's definitely wrong, by 3 orders of
> magnitude. This needs to be set to the intended default of 15 _seconds_.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
