Stops working after first send / receive command

[aidan-rypens]

I'm having some trouble using this. It works very well for one request, but sending another command to the TCP server it throws an exception.

I did look at the followings tests:
https://github.com/MojtabaKiani/Rony.Net/blob/main/tests/Rony.FunctionalTests/MockTcpServerTests.cs

Should it be able to send the mock server multiple requests (like below) or is this not how it is intended to be used?

Example code:

        const int port = 4000;
        
        const string command1 = "ping";
        const string mockResponse1 = "pong";

        const string command2 = "pong";
        const string mockResponse2 = "ping";

        var tcpServer = new MockServer(new TcpServer(port));
        tcpServer.Mock.Send(command1).Receive(mockResponse1);
        tcpServer.Mock.Send(command2).Receive(mockResponse2);

        tcpServer.Start();

        var client = new SocketClient(IPAddress.Loopback.ToString(), port);
        await client.Connect();

        await client.Send(command1);
        var response = await client.ReceiveStringResponseAsync();

        await client.Send(command2);
        var response2 = await client.ReceiveStringResponseAsync();

        response.Should().Be(response);
        response2.Should().Be(response2);

Example code without wrapper for sending / receiving:

        var hostName = IPAddress.Loopback.ToString();
        const int port = 4000;

        const string command1 = "ping";
        const string mockResponse1 = "pong";

        const string command2 = "pong";
        const string mockResponse2 = "ping";

        var tcpServer = new MockServer(new TcpServer(port));
        tcpServer.Mock.Send(command1).Receive(mockResponse1);
        tcpServer.Mock.Send(command2).Receive(mockResponse2);

        tcpServer.Start();

        var client = new TcpClient(hostName, port);
        var stream = client.GetStream();

        // SEND 1
        var byteData = ASCII.GetBytes(command1);
        await stream.WriteAsync(byteData, 0, byteData.Length);

        var buffer = new byte[1024];
        int bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length);
        var response1 = ASCII.GetString(buffer, 0, bytesRead);

        // SEND 2
        byteData = ASCII.GetBytes(command2);
        await stream.WriteAsync(byteData, 0, byteData.Length);

        bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length);
        var response2 = ASCII.GetString(buffer, 0, bytesRead);

[archofthings]

Hey. I will take a look

[aidan-rypens]

Thanks. Seems to be also an issue when I use your project.
As a workaround, it is possible to use a new TCP client everytime you send out something.

[DingbatDev]

I also faced this issue with a TcpServer. This is a great little project which I used for developing a protocol handler.

It looks to me like the ReplyAsync function is designed to close after a message has been received, and a response sent.

To make the TcpServer stay listening, I changed the following...

In TcpServer.ReplyAsync() - commented out the stream.Close() and stream.Dispose() calls.

In TcpListenerWrapper - added a "public TcpClient? Client" property.

In TcpServer.ReceiveAsync() - added the following code at the top:

            if (this.listener.Client is null || this.listener.Active == false)
            {
                // Await new connection before attempting to start reading (skipped if listener is already active)
                this.listener.Client = await this.listener.AcceptTcpClientAsync();
            }

I'm new to socket programming in C#, so I'm not sure if I have missed anything. As a small mock server, I think this works fine. More attention might be needed if using it for a production server!