[ https://issues.apache.org/jira/browse/IGNITE-12490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083015#comment-17083015 ]
Alexey Kukushkin commented on IGNITE-12490: ------------------------------------------- There is a single-node scenario causing same problem described in IGNITE-12894 > Service proxy throws "Service not found" exception right after deploy > --------------------------------------------------------------------- > > Key: IGNITE-12490 > URL: https://issues.apache.org/jira/browse/IGNITE-12490 > Project: Ignite > Issue Type: Improvement > Components: managed services > Affects Versions: 2.8 > Reporter: Alexey Goncharuk > Priority: Major > Attachments: ServiceInvokeTest.java > > > In the following scenario: > * Start nodes A, B > * Deploy a service on A > * Create a service proxy on B > * Invoke the proxy > The proxy invocation throws a service not found exception. As per discussion > [on the dev > list|http://apache-ignite-developers.2346864.n4.nabble.com/Discovery-based-services-deployment-guarantees-question-td44866.html] > this case should be handled by an automatic retry, however, it's not. > The reproducer is attached. -- This message was sent by Atlassian Jira (v8.3.4#803005)