Yep, ok.

In my case the .NET adapter is implemented using a very simple scheme for connecting to the Lighstreamer server (based on your example with establishing TCP connections to specific ports inside a console process). It is kind of the "chicken and egg" problem. The LS process must be running for the adapter to connect - but the adapter must be running for the LS startup to complete.

However, running the adapter first - and implementing retry logic (to set up the communication channels), e.g. detecting when LS server is available, should fix that problem.

For now, I have just added the timeout and that works fine.