[
https://issues.apache.org/jira/browse/IGNITE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372912#comment-15372912
]
Alexander Paschenko commented on IGNITE-3392:
---------------------------------------------
Having investigated the issue, I discovered that the reason behind this issue
is that the client completes its service deployment future at the wrong moment
- it does so on receiving cache update event, and it could hardly be correct.
As I see it now, the client rather should wait for a different event and
probably listen for different cache that would store service deployment
statuses. After having discussed it with Semen, it's currently unclear how to
fix this without major rehaul which in turn could threat with future
compatibility issues (in cases when nodes of different Ignite versions live in
the same cluster).
Anyway, the properly written test for this issue is in ignite-3392 branch.
> IgniteServices.deploy() method doesn't throw exception in case service
> initialization throws exception
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-3392
> URL: https://issues.apache.org/jira/browse/IGNITE-3392
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Alexander Paschenko
> Fix For: 1.7
>
> Attachments: Test.java
>
>
> Test that demonstrates the issue is attached. If exception is thrown from the
> {{Service.init()}} method, it's only printed out on the server not propagated
> to the client. If client then tries to get the proxy, it goes to infinite
> loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
