Use parameter SQLNET.EXPIRE_TIME to specify a the time interval, in minutes, to send a probe to verify that client/server connections are active. Here is what the Oracle manual says on this subject: Set the value of SQLNET.EXPIRE_TIME in sqlnet.ora. Is there some other way to keep these TOAD connections active (from either end of the communication)?.Can I use this KeepAliveTime technique on the windows client machines or maybe the server?.There are relatively few programs implementing keepalive. Programs must request keepalive control for their sockets using the setsockopt interface. Remember that keepalive support, even if configured in the kernel, is not the default behavior in Linux. This seems like the Linux system wide configuration for using system wide keep-alive.īut, that requires programs to use the setsockopt() and request keep-alive (right?). HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime Looking up a bit on system-wide configurations, I came up with this Microsoft TechNet detail on Configuring system wide Keep-Alives that involves working with the KeepAliveTime and related registry variables.
I have fixed this problem for PuTTY idle connections īut, I have not yet identified any such support in the TOAD software. Of course, it does not support longer timeouts for specific flows. It is not acceptable to increase the timeout on the firewall globally and These sessions could be idle for multiple hours! I have a scenario where long-idle sessions of TOADSoft client communication with the Oracle server seem to be torn down as they timeout on an intermediate state-full firewall.
0 kommentar(er)
