The server does not receive the message when it has successfully sent the message and closes the application immediately

[binbon2d]

I have a problem in implementing a Client Console to send messages to the Server
As soon as the Console is connected to the Server I send a message and close the Console and the bad thing happened, the Server couldn't receive my message.
To solve this problem I had to let the console sleep for 500ms before closing it.
I want to ask the cause and how to fix it effectively, I can't keep my Console open all the time.

[jchristn]

Hi @binbon2d could you share a small code sample that highlights this problem? An alternative would be to use a SendAndWait method.

[jchristn]

Ok, so this is actually a really hard problem to solve, but thankfully there are two viable solutions. I tried hacking apart the logic for reading from a stream to actually return the data in the event of an exception (in case the message was fully read, you still want to process it). That led to a rat's nest of problems.

However, something I found which may be useful in your case is wrapping your instance of WatsonTcpClient in a using block. That way, when it's done, it naturally calls .Dispose(). I tested this with the Test.FastDisconnect project, and was able to receive the message correctly.

Or, add a Task.Delay, Thread.Sleep, or something else.

[jchristn]

Example:

using System;
using WatsonTcp;

namespace Test.FastDisconnect
{
    class Program
    {
        static void Main(string[] args)
        {
            try
            {
                using (WatsonTcpClient client = new WatsonTcpClient("127.0.0.1", 9000))
                {
                    client.Events.MessageReceived += MessageReceived;
                    client.Connect();
                    client.Send("Hello!");
                }
            }
            catch (Exception e)
            {
                Console.WriteLine(e.ToString());
            }
        }

        static void MessageReceived(object sender, MessageReceivedEventArgs args)
        {

        }
    }
}

[binbon2d]

Thank you for your quick reply
I implemented according to your suggestion using using Block but the first time Star Server & Client still lost data

1. Start Server
2. Start Client & Connect
3. Client Send Message

If don't turn off the Server App, next second sending everything works fine

Temporarily this this problem does not affect my project too much, I will always follow you if there is a new version of WatsonTcp it has been helping me a lot for my work

Thank you very much

[binbon2d]

By the way, can you tell me if there is an Event on the Server side for IdleClientTimeout ?

I setting :
server.Settings.IdleClientTimeoutSeconds = 0;
or
server.Settings.IdleClientTimeoutSeconds = Int32.MaxValue;

The client does not communicate with the server for a period of time.
I feel that the Client has been TimeOut and the Server is not aware of this

I want my Client to always connect to the Server, what should I do?

[jchristn]

Hi @binbon2d sorry for the delay. There is no event indicating a timeout, but the Events.ClientDisconnected event uses the DisconnectionEventArgs, and Reason should be populated with Timeout. Please let me know if that's not the case.

I just tested using the Test.Server and Test.Client project, and the reason is indeed populated.

Client

C:\Code\Watson\WatsonTcp\src\Test.Client\bin\Debug\net7.0>test.client
Server IP: [localhost]
Server port: [9000]
Use SSL: [y/N]?
[Info     ] [WatsonTcpClient] connecting to localhost:9000
Server connected
[Info     ] [WatsonTcpClient] connected to localhost:9000
Command [? for help]: [Info     ] [WatsonTcpClient] disconnect due to timeout
[Debug    ] [WatsonTcpClient] data receiver terminated for localhost:9000
Server disconnected: Timeout

Server:

_Server.Settings.IdleClientTimeoutSeconds = 5;