Hello, Well, it seems that peer deployment does work with peer class loading. The problem I described is with method invocation with arguments that includes classes from the service classpath.
Regards On Tue, Jun 2, 2015, 08:04 yakov [via Apache Ignite Users] < [email protected]> wrote: > Correct link is https://issues.apache.org/jira/browse/IGNITE-975 > > --Yakov > > 2015-06-02 13:03 GMT+03:00 Yakov Zhdanov <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=440&i=0>>: > >> 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 <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=440&i=1>>: >> >>> 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. >>> >> >> > If you reply to this email, your message will be added to the discussion > below: > > http://apache-ignite-users.70518.x6.nabble.com/Failed-to-unmarshal-service-method-arguments-tp437p440.html > To unsubscribe from Failed to unmarshal service method arguments, click > here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=437&code=dGNvc3Rhc291emFAZ21haWwuY29tfDQzN3wtMTI3MjQ2NDcyNQ==> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-unmarshal-service-method-arguments-tp437p441.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
