-
L.S., The past few months, I've been breaking my head on bi-directional Ice connections. So a "worker" (client) connects to an "orchestrator" (server) that orchestrates workloads to various workers. The worker connects to the orchestrator fine. Then the orchestrator wants to set up the worker (load an algorithm) over the same connection. I keep getting the following server/orchestrator error (with varying UUIDs):
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi, Seems that you forget to provide the |
Beta Was this translation helpful? Give feedback.
The
ice_fixed
method returns a new fixed proxy instead of mutating the existing one. Proxy types in Ice are immutable, and theice_xxx
methods return a new proxy with the updated setting.See https://doc.zeroc.com/ice/3.7/client-side-features/proxies/proxy-methods
In your code the
worker_i->algorithmAsync
is not using the fixed proxy, worker_i is still a regular non-fixed proxy. Then one in theworkers_
map is a fixed proxy.