Transmit Server Closed Connection.
State server was configured as 'localhost', 127.0.0.1 would not have had this issue. I check by disassembling webengine4.dll. It returns something like 'connection closed by remote host' HRESULT 72746. But system.web interprets this as the session being locked by a concurrent query and keeps retrying at full speed. This may require increasing the timeout on the network device so that long running connections are not prematurely closed. For an application server connecting to Exchange Server 2010, set the application server's TCP Keep-Alive time to a value less than the idle connection timeout window on.
Learn how to configure the timeout settings for your Load Balancer resource.
Oracle Cloud Infrastructure load balancers support connection multiplexing. The load balancer can route many incoming requests from multiple clients to the destination backend server through a few (one or multiple) backend connections.
After your load balancer connects a client to a backend server, the connection can be closed because of inactivity. Also, you can configure load balancer listeners to control the maximum idle time allowed during each TCP connection or HTTP request and response pair. Oracle recommends that you do not allow your backend servers to close connections to the load balancer.
The following timeout settings affect your load balancer's behavior:
Keep-alive setting between the load balancer and the client
The Load Balancing service sets the keep-alive value to maintain the connection for 10,000 transactions or until it has been idle for 65 seconds, whichever limit occurs first.
Keep-alive setting between the load balancer and backend server
The load balancer closes backend server connections that are idle for more than 300 seconds. See Keep-Alive Settings for more information.
Idle timeout
You can set the duration of the idle timeout when you create a listener. This setting applies to the time allowed between two successive receive or two successive send network input/output operations during the HTTP request-response phase. See Idle Timeout Settings for more information.
Keep-Alive Settings
Learn how the Load Balancer resource sets the keep-alive value to maintain a connection with backend servers.
Server Closed Connection
The Load Balancing service does not honor keep-alive settings from backend servers. The load balancer closes backend server connections that are idle for more than 300 seconds. Oracle recommends that you do not allow your backend servers to close connections to the load balancer. To prevent possible 502 errors, ensure that your backend servers do not close idle connections in less than 310 seconds.
Transmit Server Closed Connection
The Load Balancing service sets the keep-alive value to maintain the connection for 10,000 transactions or until it has been idle for 65 seconds, whichever limit occurs first.