Случайно наткнулся на следующую главу в тренинге по администрированию. Вообще-то, это про соединения с БД, но, возможно, поможет и при работе с AOS.
Dead connection detect
Problems can occur when the server does not close a connection after a PC client process has disappeared. This typically happens when a PC user switches off or reboots their machine while still connected to Oracle. This is not a direct performance issue, but if this happens for a lot of connections it will have an effect on performance
By setting sqlnet.expire_time in sqlnet.ora at sever side, you can determine
time interval to send a probe to verify the session is alive. By default the
dead connection detect is not enabled.
For Windows NT and 95 client PC a keepalive extension to TCP/IP is enabled.
Problems can occur however if the timeout period is too fast for some heavily used or slow network. Under those conditions, the KEEPALIVE registry value can be used to specify a KEEPALIVE value before a connection gets cut.
<pre>Windows NT:
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
TCP/IP
Parameters
KeepAlive: REG_DWORD "number"
Windows 95 / 98;
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
Winsock
Parameters
TcpMaxDataRetransmissions: REG_DWORD "number"</pre>
A value of '10' is a common value specified for this variable. This parameter can be useful on both client and server.
This parameter is not present in the registry by default. This means that the first time, this parameter will need to be added to this registry key. The purpose and behavior of the parameter is the same on the Windows 95 and Windows 98, as on the Windows NT platform.