service client connection state not handled correctly

[rex-schilasky]

Problem Description

Currently a service client is "connected" if a service server has been registered with the matching service name. The connection may not be established this time but the connection state is set on true.

How to reproduce

Run a client and call a matching service right after connection state gets true. This will lead to a lost rpc call.

How did you get eCAL?

I don't know

Environment

All operating systems.

eCAL System Information

No response