null
Customer found that the server did not receive the FIN/ACK message sent by the client, so each HTTP session will timeout after 5 minutes and cannot be closed immediately, consuming a lot of server resources
After capturing the packet, it was found that the terminal only sent the third wave message 2 minutes after sending the second wave, causing the FIN timer on the firewall to time out and block subsequent messages.
Modify the fin timeout of the firewall. But not recommended because it will consume a lot of firewall resources.
Recommend letting the customer to investigate the reasons for the server side's fin interval exceeding two minutes
session aging-time fin 120