You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/22 06:08:00 UTC
[jira] [Updated] (IGNITE-11302) idleConnectionTimeout TcpComm
different on server and client (client default > server custom) lead to
wait until client timeout on server side
[ https://issues.apache.org/jira/browse/IGNITE-11302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-11302:
---------------------------------------
Fix Version/s: (was: 2.9)
2.10
> idleConnectionTimeout TcpComm different on server and client (client default > server custom) lead to wait until client timeout on server side
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-11302
> URL: https://issues.apache.org/jira/browse/IGNITE-11302
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: ARomantsov
> Assignee: Dmitriy Sorokin
> Priority: Critical
> Fix For: 2.10
>
>
> Server config:
> {code:xml}
> <property name="communicationSpi">
> <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> <property name="idleConnectionTimeout" value="1000"/>
> </bean>
> </property>
> Client config
> <property name="communicationSpi">
> <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> </bean>
> </property>
> {code}
> Server wait until default idleConnectionTimeout (10 m) for client fail.
> If both config with idleConnectionTimeout=1 s - ignite worked according to config
--
This message was sent by Atlassian Jira
(v8.3.4#803005)