Split the services into 2 separate instances, one with high intensive network usage, and the one with where only Ignite clients are running didn't help, the error still persists and happens after couple hours of working.
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
