Hi! I reproduced the issue and filed a ticket: https://issues.apache.org/jira/browse/IGNITE-976
In the meantime, turn off peer-loading and make all classes available on all nodes. This configuration is much better from performance standpoint and is recommended in production. I am also cross-posting this thread to dev list in order to raise a question - should services support peer-deployment? My answer is no. Service may be implemented in the way that missing classes may be required after master node leaves, but service may be configured to stay after master leaves. So, even CONTINUOUS deployment mode does not help. --Yakov 2015-06-02 2:36 GMT+03:00 tcostasouza <[email protected]>: > Hello, > > It seems that, even with peer class loading enabled, Ignite is searching > for > a Service's method argument classes from it's root classpath. Consider de > following example: > > > > Now, start 2 Ignite nodes with peer class loading enabled. From one node, > deploy and invoke service: > > > Invocation will fail with Ignite complaining that it couldn't find > TestServiceImpl class in sun.misc.Launcher$AppClassLoader (full log here > < > http://apache-ignite-users.70518.x6.nabble.com/file/n437/ignite_exception.log > > > ) > > Now, if I change from TestService.execute(TestRequest) to something like > TestService.execute(int), then it works as expected. > > Any clue? > > Thanks > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Failed-to-unmarshal-service-method-arguments-tp437.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
