Hi! My apologies, this was a false alarm. When I used 2.0-M4 there indeed was the aforementioned problem when using Tribes. Using a recent nightly build, both Tribes and Hazelcast works as I hoped; when starting a client first and later starting a service, the service is discovered by the client and the client is able to successfully send requests to the service. Again, sorry about the false alarm. Ivan
- Clients of Distributed Nodes (with Tribes/Hazelcast) keinmensch
- Re: Clients of Distributed Nodes (with Tribes/Hazelcast) Raymond Feng
- Re: Clients of Distributed Nodes (with Tribes/Hazelc... keinmensch
