SQLNET.INBOUND_CONNECT_TIMEOUT

[复制链接]
查看11 | 回复2 | 2013-1-28 09:12:18 | 显示全部楼层 |阅读模式
1. In server side sqlnet.ora file add
SQLNET.INBOUND_CONNECT_TIMEOUT
For e.g
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
2. In listener.ora file -
INBOUND_CONNECT_TIMEOUT_ = 110
For e.g if the listener name is LISTENER then -
INBOUND_CONNECT_TIMEOUT_LISTENER = 110

这两个超时的时间参数不一样大小以哪个为准呢?我测试了一下谁大就以谁为准。不知道对不对?

回复

使用道具 举报

千问 | 2013-1-28 09:12:18 | 显示全部楼层
if you need to explicitly set a different value, then Oracle recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying the values for these parameters, note the following recommendations:
Set both parameters to an initial low value.
Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and SQLNET.INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed.

回复

使用道具 举报

千问 | 2013-1-28 09:12:18 | 显示全部楼层
过过招 发表于 2012-5-28 10:21
if you need to explicitly set a different value, then Oracle recommends setting this parameter in co ...

意思是看明白了。还有个问题是为什么我在服务器上的 sqlnet.ora文件设置了。SQLNET.EXPIRE_TIME=1
但是重启监听好像没有起作用。先前模拟断网但是会话还在的死连接并没有被清除。为什么?
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行