Now in ignite configurations in many network related parameters (for example: IgniteConfiguration.netTimeout, TcpDiscoverySpi.socketTimeout, TcpDiscoverySpi.ackTimeout) used long. But network socket using int for socket timeout, so we do simple "(int)timeout" type casting and if timeout value > Integer.MAX_VALUE - get exception. The question is: why we use long type?
- Using long for configure network timeouts Sasha Belyak
- Re: Using long for configure network timeouts Yakov Zhdanov