/commented by dmitriy setrakyan/ It looks like Ignite instance is in the scope of your clustered code and also gets serialized.
If you are using default Ignite OptimizedMarshaller or JdkMarshaller, then they honor the Java Serializable and Externalizable contracts. This way, classes like Ignite or any other Ignite artifacts get properly serialized. However, in your own marshaller perhaps you have some different logic which does not work with Externalizable interface. To avoid serializing Ignite instance by accident, I would isolate the closure or task logic you are sending to the cluster into a static class. Please let me know if it fixes your issue. ----- /This post is migrated from now discontinued Apache Ignite forum at http://apacheignite.readme.io/v1.0/discuss/ -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Custom-Marshaller-tp12p15.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
