Hey! There is a test, that is very similar to what you described: GridServiceProxyClientReconnectSelfTest#testClientReconnect <https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/service/GridServiceProxyClientReconnectSelfTest.java#L60> It is passing on master and on ignite-2.4 Could you take a look and tell if it's different from your case? If it is, please write a test, that reproduces your issue.
Denis вт, 15 мая 2018 г. в 19:33, wangsan <[email protected]>: > i see some bugs such as https://issues.apache.org/jira/browse/IGNITE-2766 > <https://issues.apache.org/jira/browse/IGNITE-2766> > https://github.com/apache/ignite/pull/2627 > <https://github.com/apache/ignite/pull/2627> > when i apply the patch, cache can be reused when client reconnect. but > igniteservice can not be reused. > the ex as follows: > > Caused by: java.lang.IllegalStateException: class > org.apache.ignite.internal.processors.cache.CacheStoppedException: Failed > to > perform cache operation (cache is stopped): ignite-sys-cache > at > > org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164) > at > > org.apache.ignite.internal.processors.cache.affinity.GridCacheAffinityProxy.mapKeyToNode(GridCacheAffinityProxy.java:202) > at > > org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceTopology(GridServiceProcessor.java:931) > at > > org.apache.ignite.internal.processors.service.GridServiceProxy.randomNodeForService(GridServiceProxy.java:274) > at > > org.apache.ignite.internal.processors.service.GridServiceProxy.nodeForService(GridServiceProxy.java:260) > at > > org.apache.ignite.internal.processors.service.GridServiceProxy.invokeMethod(GridServiceProxy.java:170) > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
