RST packet sent from application when TCP connection not getting closed properly -

I have a web service based application where the web server is running on application on a particular port in recent production In the environment, I have found that this application is sending a RST packet to the client to reset the connection. After analyzing the TCP dump, I have seen that the TCP 4 method is not being properly formed due to the closure of the connection. After sending a response from the client to the application web server, this application is sending a FIN packet to the client and receives the ACK, but no finet packet is initiated from the client, instead it receives some request packets. At this point, the application sends a RST packet to the customer because the application was expecting the introduction of FIN packet from the client. This causes loss of request packets. I believe this web server is a normal / expected behavior of the application and should be fixed in the client side.

Please comment on the above scenario.

The status of the EOS on the socket is ignoring the customer and continue to write the client again by peer 'Connection reset' is basically an application protocol error, either the customer should not send the second request to the same connection or the server should first search for it instead of closing the connection after the connection.