Ok thanks Val. Btw, during testing I noticed that because of this issue, if I had a node in my cluster that did not have the proper jar file deployed to, and the current node the service was running on went down, if Ignite tried to re-instantiate the cluster singleton service on the node that didn't have the right jar, it would throw exception and hang, thereby never being able to re-instantiate that service on another node. This behavior breaks the guarantee that Ignite will always have an instance of the service running despite topology changes. For now it may be enough to make special note in the documentation that this service up guarantee is only valid if all dependent jars have been manually deployed to each node in the cluster.
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ServiceGrid-and-Peer-class-loading-tp1089p1106.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
