ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thammoud <thamm...@yahoo.com>
Subject Re: Socket Closure due to write timout
Date Wed, 20 Jul 2016 11:42:25 GMT
Hi Val,

TcpCommunicationSpi.setMessageQueueLimit is the one that resolved the issue.
I increased it a lot. The timeout is not a result of an unstable network. I
do run multiple instances on the same machine. The timeout is not a result
of a socket error but a function of how long a worker takes to accomplish
the task. The example that I attached earlier clearly shows the behavior.
The lower the thread sleep in the worker, the lower the chances of getting
the error. 

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Socket-Closure-due-to-write-timout-tp6391p6418.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message