This is possible under some circumstances, see this ticket (should be fixed soon): https://issues.apache.org/jira/browse/IGNITE-3197
This exception should be harmless, only flooding the logs. Is this the case for you? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-when-starting-second-node-tp5164p5189.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
