Marco wrote > Thank you for the reply, yes, this REST-API project could save a lot of > time. > <br/> > Last month, we launched a jetty project to wrap ignite client node, > <br/> > (Jetty-->RESTController(Query/Put/Get)-->Ignite Client Node) > <br/> > glassfish can do the interpretation between java object and json, but we > keep suffering from some connection exceptions. > <br/> > <br/> > 09:45:21,319 ERROR REST_Put2Ignite:31 - class > org.apache.ignite.IgniteClientDisconnectedException: Operation has been > cancelled (client node disconnected). > <br/> > <br/>
This exception is thrown when the client loses connectivity with servers due to network issues, or if all servers are down for some reason. Did you check server logs? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/The-custom-object-support-in-REST-API-tp6393p6424.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
