[jira] [Created] (IGNITE-11302) idleConnectionTimeout TcpComm different on server and client (client default > server custom) lead to wait until client timeout on server side

[Anton Vinogradov (Jira)]

ARomantsov created IGNITE-11302:
-----------------------------------

             Summary: 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
             Fix For: 2.8


Server config:
        <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>

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
(v7.6.3#76005)