Hi, Actually I don't see an actual error from the logs provided by you that had caused an abnormal behavior on your side.
DEBUG messages related to communication issues are normal. They tend to appear when a connection to an expected node is lost or can't established by some reason. The only ERROR message (Failed to deserialize object with given class loader sun.misc.Launcher$AppClassLoader) should be treated as a DEBUG one as well because it doesn't bring the system into an unstable. In your particular case I see that the node with ID da388f98-2a1d-4cd8-b464-77b27ca743f3 and address addr=/10.1.XXXX,port=11547,localport=47500 left topology by some reason. The rest of the nodes detected this and as a result you got all these DEBUG messages. Please check the logs of da388f98-2a1d-4cd8-b464-77b27ca743f3 node and share them with us if you need more help on this. BTW, you mentioned that the grid stopped working. What do you mean under that? Was the grid hanging and you had to restart it or it stopped because your app shut id down when an exception was detected? Finally, please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to “ [email protected]” and follow simple instructions in the reply. Regards, Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Grid-stopped-with-IgniteCheckedException-Failed-to-deserialize-object-with-given-class-loader-sun-mir-tp2123p2124.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
