[
https://issues.apache.org/jira/browse/IGNITE-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-3361.
----------------------------------
Resolution: Fixed
Fixed in master (commit 55e616f).
> Service is not redeployed after a node is left topology
> -------------------------------------------------------
>
> Key: IGNITE-3361
> URL: https://issues.apache.org/jira/browse/IGNITE-3361
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Denis Magda
> Assignee: Semen Boikov
> Priority: Blocker
> Fix For: 1.7
>
> Attachments: SingletonServiceLostAfterToplogyChangeMain.java
>
>
> In attach you will find an example demonstrating the issue when a service is
> not being redeployed after several nodes are started and stopped.
> The stack trace of the issue is the following
> {code}
> Exception in thread "main" class org.apache.ignite.IgniteException: Failed to
> find deployed service: DummyService
> at
> org.apache.ignite.internal.processors.service.GridServiceProxy$ProxyInvocationHandler.invoke(GridServiceProxy.java:168)
> at com.sun.proxy.$Proxy24.foo(Unknown Source)
> at
> org.apache.ignite.examples.SingletonServiceLostAfterToplogyChangeMain.failingSequence(SingletonServiceLostAfterToplogyChangeMain.java:95)
> at
> org.apache.ignite.examples.SingletonServiceLostAfterToplogyChangeMain.main(SingletonServiceLostAfterToplogyChangeMain.java:18)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
