) Clients can't operate on
services after deactivation
Raymond,
The issue here is that client connections lose subscriptions to events,
related to service deployment.
So, clients can deploy services to other nodes, but they don't return
execution from *IgniteServices#deploy* *met
Raymond,
The issue here is that client connections lose subscriptions to events,
related to service deployment.
So, clients can deploy services to other nodes, but they don't return
execution from *IgniteServices#deploy* *methods.
The workaround here is to restart clients, that were present in th
Hi Raymond,
I thought 2.5 is already freezed.
Several days remained to release (vote), so it is not likely this issue can
be done.
Probably Denis M. or Andrey G. could correct me if I'm wrong.
Sincerely,
Dmitriy Pavlov
пн, 16 апр. 2018 г. в 21:52, Raymond Wilson :
> Hi Denis,
>
> Would this be
Hi Denis,
Would this be better to target 2.5? It seems like a significant regression...
Thanks,
Raymond.
Sent from my iPhone
> On 17/04/2018, at 1:46 AM, Denis Mekhanikov (JIRA) wrote:
>
> Denis Mekhanikov created IGNITE-8279:
>
>
> Summa
Denis Mekhanikov created IGNITE-8279:
Summary: Clients can't operate on services after deactivation
Key: IGNITE-8279
URL: https://issues.apache.org/jira/browse/IGNITE-8279
Project: Ignite
