ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Calling serviceDescriptiors after service deployment throws exception
Date Tue, 28 Jun 2016 00:48:27 GMT

This happens because you save Ignite instance in the service and it then
can't be deserialized in the user thread. Generally, I would recommend to
avoid serialization of Ignite, IgniteCache and similar objects. To do this
you can inject Ignite into the service like this:

class MyService implements Service {
    private transient Ignite ignite;


Ignite instance will be injected automatically on the node where the service
is deployed.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Calling-serviceDescriptiors-after-service-deployment-throws-exception-tp5903p5937.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message