oracle keep alive,[20200220]windows设置keepalive参数.txt

最新推荐文章于 2023-04-21 10:46:50 发布
最新推荐文章于 2023-04-21 10:46:50 发布
阅读量680 收藏
点赞数
文章标签： oracle keep alive

[20200220]windows设置keepalive参数.txt

--//昨天测试了ENABLE=BROKEN在连接串中，可以发现在客户端启用了TCP keep-alive feature特性。而缺省tcp_keepalive_time设置

--//7200秒，时间有点长。许多客户端或者中间服务器使用的是windows系统，如何修改注册表呢？

--//检索找到如下链接：http://www.cppblog.com/Robertxiao/articles/153510.html

1)在Windows NT平台上， 我们利用regedit来修改系统注册表，修改

HKEY_LOCAL_MACHINE\CurrentControlSet\Services\Tcpip\Parameters下的以下三个参数：

KeepAliveInterval        :设置其值为1000

KeepAliveTime            :设置其值为300000(单位为毫秒，300000代表5分钟)

TcpMaxDataRetransmissions:设置其值为5

--//在我的工作机器测试看看。注：我的测试环境是windows 7.

1.修改注册表:

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]

"KeepAliveTime"=dword:00001770

"KeepAliveInterval"=dword:000003e8

"MaxDataRetries"="5"

--//KeepAliveTime=0x1770 = 6000

--//KeepAliveInterval=0x000003e8 = 1000

--//注：不知道MaxDataRetries还是TcpMaxDataRetransmissions，windows 技术资料太少。那位知道，我最终测试2个不是。

--//或者像https://blog.csdn.net/shenya1314/article/details/70187767介绍那样，客户端无法设置。

2.测试：

--//服务端设置：

# echo /proc/sys/net/ipv4/tcp_keepalive* | xargs   -n 1  strings -1 -f

/proc/sys/net/ipv4/tcp_keepalive_intvl: 75

/proc/sys/net/ipv4/tcp_keepalive_probes: 9

/proc/sys/net/ipv4/tcp_keepalive_time: 7200

$ grep SQLNET.EXPIRE_TIME $ORACLE_HOME/network/admin/sqlnet.ora

#SQLNET.EXPIRE_TIME = 1

--//延长服务端tcp_keepalive_time时间，避免服务端干扰。

sqlplus scott/book@"(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_DATA=(SERVICE_NAME=book)(SERVER = DEDICATED))(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.78)(PORT=1521)))"

SCOTT@book> @ spid

SID    SERIAL# PROCESS                  SERVER    SPID                     PID  P_SERIAL# C50

---------- ---------- ------------------------ --------- -------------------- ------- ---------- --------------------------------------------------

3       2097 1688:7476                DEDICATED 21518                     24        159 alter system kill session '3,2097' immediate;

# netstat -npo 2>/dev/null | grep 21518

tcp        0      0 192.168.100.78:1521         192.168.98.6:56411          ESTABLISHED 21518/oraclebook    keepalive (7177.06/0/0)

--//确定端口号 56411

# tcpdump -vvnni eth0  port 56411

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

--//等1分钟毫无反应。噢！才想起来也许要重启机器再测试。不知道断开网络再连接是否有效，先测试禁用再启用连接的情况。

3.继续测试：

--//禁用再启用网络连接，操作细节略。

sqlplus scott/book@"(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_DATA=(SERVICE_NAME=book)(SERVER = DEDICATED))(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.78)(PORT=1521)))"

SCOTT@book> @ spid

SID    SERIAL# PROCESS                  SERVER    SPID                     PID  P_SERIAL# C50

---------- ---------- ------------------------ --------- -------------------- ------- ---------- --------------------------------------------------

58       1379 8420:2824                DEDICATED 21635                     28        114 alter system kill session '58,1379' immediate;

# netstat -npo 2>/dev/null | grep 21635

tcp        0      0 192.168.100.78:1521         192.168.98.6:57543          ESTABLISHED 21635/oraclebook    keepalive (7084.23/0/0)

--//确定端口号 57543

# tcpdump -vvnni eth0  port 57543

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

--//等1分钟毫无反应。

4.再继续测试：

--//重启测试机器客户端。

sqlplus scott/book@"(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_DATA=(SERVICE_NAME=book)(SERVER = DEDICATED))(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.100.78)(PORT=1521)))"

SCOTT@book> @ spid

SID    SERIAL# PROCESS                  SERVER    SPID                     PID  P_SERIAL# C50

---------- ---------- ------------------------ --------- -------------------- ------- ---------- --------------------------------------------------

58       1391 4052:5612                DEDICATED 22059                     28        119 alter system kill session '58,1391' immediate;

$ netstat -npo 2>/dev/null | egrep "22059"

tcp        0      0 192.168.100.78:1521         192.168.98.6:49682          ESTABLISHED 22059/oraclebook    keepalive (7163.03/0/0)

# tcpdump -vvnni eth0  port 49682

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

10:06:23.007811 IP (tos 0x0, ttl 127, id 3580, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 3057020812:3057020813(1) ack 1803888726 win 16289

10:06:23.007991 IP (tos 0x0, ttl  64, id 63755, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

10:06:29.010284 IP (tos 0x0, ttl 127, id 3611, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:06:29.010324 IP (tos 0x0, ttl  64, id 63756, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

10:06:35.004759 IP (tos 0x0, ttl 127, id 3656, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:06:35.004797 IP (tos 0x0, ttl  64, id 63757, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

10:06:41.013022 IP (tos 0x0, ttl 127, id 3695, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:06:41.013075 IP (tos 0x0, ttl  64, id 63758, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

--//总算OK了。注意看时间间隔正好6秒。

10:09:23.021838 IP (tos 0x0, ttl 127, id 4958, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:09:23.021929 IP (tos 0x0, ttl  64, id 63785, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

# iptables -I INPUT 1 -p tcp --dport 49682 -j drop

--//奇怪执行以上命令不行。因为没有这样类型的包。

--//192.168.100.78.1521 > 192.168.98.6.49682 对应的是OUTPUT链。

# iptables -D INPUT 1

# iptables -I INPUT 1 -p tcp --sport 49682 -j DROP

10:15:59.099141 IP (tos 0x0, ttl 127, id 7794, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:15:59.099179 IP (tos 0x0, ttl  64, id 63851, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49682: ., cksum 0x47cc (incorrect (-> 0x63a3), 1:1(0) ack 1 win 330

--//正常。以下就是执行iptables -I INPUT 1 -p tcp --sport 49682 -j DROP的情况。

10:16:05.101208 IP (tos 0x0, ttl 127, id 7848, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:06.102474 IP (tos 0x0, ttl 127, id 7850, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:07.103134 IP (tos 0x0, ttl 127, id 7859, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:08.103356 IP (tos 0x0, ttl 127, id 7861, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:09.103903 IP (tos 0x0, ttl 127, id 7870, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:10.102031 IP (tos 0x0, ttl 127, id 7872, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:11.100107 IP (tos 0x0, ttl 127, id 7880, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:12.100189 IP (tos 0x0, ttl 127, id 7884, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:13.100203 IP (tos 0x0, ttl 127, id 7892, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:14.100300 IP (tos 0x0, ttl 127, id 7895, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49682 > 192.168.100.78.1521: ., cksum 0xa6ea (correct), 0:1(1) ack 1 win 16289

10:16:15.100914 IP (tos 0x0, ttl 127, id 7903, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.98.6.49682 > 192.168.100.78.1521: R, cksum 0xe687 (correct), 1:1(0) ack 1 win 0

--//出现11次，时间间隔1秒也正确。出现11次说明注册表的这个参数MaxDataRetries不对。

--//客户端执行sql语句，马上报错。

10:12:18 SCOTT@book> set time on escape on

10:12:20 SCOTT@book> select sysdate from dual ;

select sysdate from dual

*

ERROR at line 1:

ORA-03135: connection lost contact

Process ID: 22059

Session ID: 58 Serial number: 1391

5.验证重试测试是那个参数:

https://blog.csdn.net/shenya1314/article/details/70187767

其中， setsockopt 设置了 keepalive 模式，但是系统对 keepalive 默认的参数可能不符合我们的要求，比如空闲 2 小时后才探测对

端是否活跃，所以 WSAIoctl 函数通过 tcp_keepalive 结构体对这些参数进行了相应设置。 tcp_keepalive 这 个 结构体在 mstcpip.h

头文件中有定义：

struct tcp_keepalive {

ULONG onoff ;   // 是否开启 keepalive

ULONG keepalivetime ;  // 多长时间( ms )没有数据就开始 send 心跳包

ULONG keepaliveinterval ; // 每隔多长时间( ms ) send 一个心跳包，

// 发 5 次 (2000 XP 2003 默认 ), 10 次 (Vista 后系统默认 )

};

这个结构体设置了空闲检测时间，及检测时重复发送的间隔时间。详细的可以查询 msdn:(VS.85).aspx 。

按照 msdn 上的说法，这些参数也可以通过在注册表里设置，分别为：

HKLM/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/KeepAliveTime

HKLM/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/KeepAliveInterval

另外，有些人可能已经发现了， tcp_keepalive 这个结构体中没有对重试次数这个参数的设置，这个参数可以通过注册表来设置，具体位置为：

HKLM/SYSTEM/CurrentControlSet/Services/Tcpip/Parameters/TcpMaxDataRetransmissions

关于在注册表中设置这几个参数，我在 XP 和 Server2008 系统中都没有找到， msdn 上说貌似只是支持 server 2003 ，我这里没有实验，具体不太清楚。

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]

"KeepAliveTime"=dword:00001770

"KeepAliveInterval"=dword:000003e8

"MaxDataRetries"="5"

"TcpMaxDataRetransmissions"="5"

--//再次重启测试，其它步骤不再贴出。

# tcpdump -vvnni eth0  port 49513

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

10:41:35.694775 IP (tos 0x0, ttl 127, id 3395, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 4042311713:4042311714(1) ack 2224808308 win 16289

10:41:35.694958 IP (tos 0x0, ttl  64, id 4842, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49513: ., cksum 0x47cc (incorrect (-> 0xd828), 1:1(0) ack 1 win 330

10:41:41.692546 IP (tos 0x0, ttl 127, id 3440, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:41:41.692584 IP (tos 0x0, ttl  64, id 4843, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49513: ., cksum 0x47cc (incorrect (-> 0xd828), 1:1(0) ack 1 win 330

10:41:47.694272 IP (tos 0x0, ttl 127, id 3514, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:41:47.694313 IP (tos 0x0, ttl  64, id 4844, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49513: ., cksum 0x47cc (incorrect (-> 0xd828), 1:1(0) ack 1 win 330

10:41:53.697620 IP (tos 0x0, ttl 127, id 3586, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:41:53.697664 IP (tos 0x0, ttl  64, id 4845, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.100.78.1521 > 192.168.98.6.49513: ., cksum 0x47cc (incorrect (-> 0xd828), 1:1(0) ack 1 win 330

# iptables -I INPUT 1 -p tcp --sport 49513 -j DROP

10:41:59.696732 IP (tos 0x0, ttl 127, id 3653, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:00.691771 IP (tos 0x0, ttl 127, id 3666, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:01.691836 IP (tos 0x0, ttl 127, id 3675, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:02.691884 IP (tos 0x0, ttl 127, id 3686, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:03.692474 IP (tos 0x0, ttl 127, id 3698, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:04.695563 IP (tos 0x0, ttl 127, id 3717, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:05.695603 IP (tos 0x0, ttl 127, id 3725, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:06.696245 IP (tos 0x0, ttl 127, id 3736, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:07.697502 IP (tos 0x0, ttl 127, id 3744, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:08.698103 IP (tos 0x0, ttl 127, id 3755, offset 0, flags [DF], proto: TCP (6), length: 41) 192.168.98.6.49513 > 192.168.100.78.1521: ., cksum 0x420f (correct), 0:1(1) ack 1 win 16289

10:42:09.697217 IP (tos 0x0, ttl 127, id 3764, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.98.6.49513 > 192.168.100.78.1521: R, cksum 0x81ac (correct), 1:1(0) ack 1 win 0

--//还是不对，放弃测试。

总结：

1.windows 测试真心的烦，一共重启3次。不知道修改注册表如何快速生效。

2.知道如何修改注册表的相关信息的具体位置。

3.重试次数默认好像是10次，我设置的"MaxDataRetries"="5"，"TcpMaxDataRetransmissions"="5"或者根本不能改变。看链接：

(v=vs.85)?redirectedfrom=MSDN

/* Argument structure for SIO_KEEPALIVE_VALS */

struct tcp_keepalive {

u_long  onoff;

u_long  keepalivetime;

u_long  keepaliveinterval;

};

The value specified in the onoff member determines if TCP keep-alive is enabled or disabled. If the onoff member is set

to a nonzero value, TCP keep-alive is enabled and the other members in the structure are used. The keepalivetime member

specifies the timeout, in milliseconds, with no activity until the first keep-alive packet is sent. The

keepaliveinterval member specifies the interval, in milliseconds, between when successive keep-alive packets are sent if

no acknowledgement is received.

The SO_KEEPALIVE option, which is one of the SOL_SOCKET Socket Options, can also be used to enable or disable the TCP

keep-alive on a connection, as well as query the current state of this option. To query whether TCP keep-alive is

enabled on a socket, the getsockopt function can be called with the SO_KEEPALIVE option. To enable or disable TCP

keep-alive, the setsockopt function can be called with the SO_KEEPALIVE option. If TCP keep-alive is enabled with

SO_KEEPALIVE, then the default TCP settings are used for keep-alive timeout and interval unless these values have been

changed using SIO_KEEPALIVE_VALS.

The default settings when a TCP socket is initialized sets the keep-alive timeout to 2 hours and the keep-alive interval

to 1 second. The default system-wide value of the keep-alive timeout is controllable through the KeepAliveTime registry

setting which takes a value in milliseconds. The default system-wide value of the keep-alive interval is controllable

through the KeepAliveInterval registry setting which takes a value in milliseconds.

On Windows Vista and later, the number of keep-alive probes (data retransmissions) is set to 10 and cannot be changed.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--//这里提示不能改变。

On Windows Server 2003, Windows XP, and Windows 2000, the default setting for number of keep-alive probes is 5. The

number of keep-alive probes is controllable through the TcpMaxDataRetransmissions and PPTPTcpMaxDataRetransmissions

registry settings. The number of keep-alive probes is set to the larger of the two registry key values. If this number

is 0, then keep-alive probes will not be sent. If this number is above 255, then it is adjusted to 255.

weixin_39965673
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
keepAlive.zip
04-13
keepalive
vue组件 keep-alive 和 transition 使用详解
10-16
主要介绍了vue组件 keep-alive 和 transition 使用详解,需要的朋友可以参考下
springboot-keepalive设置测试
03-26
springboot keepalive 服务端，客户端测试
keepalive1.1.17.zip
05-21
mysql主主复制+keepalive 这是keepalive1.1.17.tar.gz
vue keep-alive 动态删除组件缓存的例子
10-16
今天小编就为大家分享一篇vue keep-alive 动态删除组件缓存的例子，具有很好的参考价值，希望对大家有所帮助。一起跟随小编过来看看吧
oracle ENABLE=BROKEN
sinbada118的博客
11-18 1038
如果一个空闲的DB连接，在防火墙设置的TCP超时时间内没有活动，就会被防火墙切断连接。 为了防止DB连接被切断，其中一个方法就是在连接描述里加上ENABLE=BROKEN，比如： jdbc:oracle:thin:@(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=myhost))(CONNECT_DATA=(SID=orcl))) ...
oracle enable broken,[20200220]关于SQLNET.EXPIRE_TIME and ENABLE=BROKEN的总结.txt
weixin_39539684的博客
04-13 427
[20200220]关于SQLNET.EXPIRE_TIME and ENABLE=BROKEN的总结.txt--//昨天做了大量关于SQLNET.EXPIRE_TIME and ENABLE=BROKEN的测试，晚上再仔细看，测试做的有点乱。--//做一些总结：1. 12c之前设置SQLNET.EXPIRE_TIME在sqlnet.ora文件中,DCD判断链接并不使用TCP keep-alive...
TCP的保活时间
softmanfly的专栏
10-05 3333
TCP保活（TCP keepalive） 作者：易隐者 发布于：2012-10-15 11:30 Monday 分类：网络分析 TCP保活的缘起        双方建立交互的连接，但是并不是一直存在数据交互，有些连接会在数据交互完毕后，主动释放连接，而有些不会，那么在长时间无数据交互的时间段内，交互双方都有可能出现掉电、死机、异常重启等各种意外，当这些意外发生之后，这些TCP连接并未
oracle adg keepalive,Oracle ADG + Keepalived 切换演练
weixin_32905035的博客
04-09 365
客户的一套生产环境采用的架构是Oracle ADG + Keepalived，近期需要进行切换演练，要求我这边保障。ADG本身切换倒没啥可说的，但引入keepalived软件，就需要提前研究下这个架构。其实看了下环境配置，整体思路也非常简单，说白了就是利用keepalived软件引入一个VIP，应用侧只需配置连接这个VIP即可。依据当前生产环境架构模拟了一套自己的测试环境。1.Keepalived...
oracle连接
AntHub的博客
04-15 385
使用JDBC创建的数据库tcp连接是没有设置keepalive的，这点可以通过Linux的netstat或ss命令在数据库客户端（即应用端）验证 使用命令netstat-ano或ss-ano，其中参数。都是显示timerit时器，timerit时器在连接建立状态下可以对连接保活计时 netstat命令对没有开启keepalive的tcp连接显示为：off（0.00/0/0） ss命令对没有keep...
Vue中对iframe实现keep alive无刷新的方法
01-19
前言 最近一个需求，需要在 Vue 项目中加入 含有iframe 的页面，同时在路由切换的过程中，要求iframe的内容 不会被刷新 。一开始使用了Vue自带的keep- alive发现没有用，于是自己研究了一下解决方案。。。。。。 Vue的keep-alive原理 要实现对保持iframe页的状态。我们先搞清楚为什么Vue的keep-alive不能凑效。keep-alive原理是把组件里的节点信息保留在了 VNode （在内存里），在需要渲染时候从Vnode渲染到真实DOM上。iframe页里的内容并不属于节点的信息，所以使用keep-alive依然会重新渲染iframe内的内容。 另外
Oracle 数据库连接池
weixin_33835690的博客
10-11 352
jdbc:oracle:thin:@(DESCRIPTION=(failover=on)(enable=broken)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=172.110.120.10)(PORT=1521))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=DBName)(failover_mode=(t...
oracle enable broken,使用带有即时客户端的cx\u Oracle的任意选择失败
weixin_39827585的博客
04-13 181
我试图使用cx\u ORACLE从oracle12c数据库中选择数据，但得到了一个异常：“cx_Oracle.OperationalError错误：ORA-03113：通信信道上的文件结束”。你知道吗我的查询在使用Pycharm时表现良好(jdbc:甲骨文：瘦驱动程序)。但是，在python3.6中使用cx\u Oracle时，除非我将in子句中的id数从500减少到大约250，否则查询将失败。这...
甲骨文服务器保活脚本(Oracle keep alive)
spiritLHL的博客
02-03 1965
所有资源都是动态占用，实时调整，避免服务器有别的任何资源已经超过限额了仍然再占用资源。适配系统：暂时已在Ubuntu中验证无问题，别的主流系统应该也没有问题可选占用：CPU，内存，带宽。
Oracle RAC负载均衡和透明应用失败切换的配置和测试过程（二、配置实例）
weixin_33826609的博客
11-19 98
第2节  配置实例主要包括的是服务器端的init.ora,listener.ora和tnsnames.ora文件以及客户端的tnsnames.ora文件。针对本项目的双节点的群集设置，主要配置如下：hostname  service name  sid name  instance_name  ORACLE_HOME========  ===========  ========   =======...
oracle enable broken,[20200219]strace跟踪设置ENABLE=BROKEN的情况.txt
weixin_42374930的博客
04-13 339
[20200219]strace跟踪设置ENABLE=BROKEN的情况.txt--//使用strace跟踪设置ENABLE=BROKEN的情况.--//开始我以为使用strace-f跟踪sqlplus+连接串，就可以获得服务端与客户端进程的相关信息，实际上错了，--//服务端端程序通过监听进程tnslsnr派生出来的，跟踪要跟踪2个进程。1.环境：SCOTT@book> @ ver1POR...
linux，windows keepalive参数的查看与设置
热门推荐
化天际的相遇---博客
11-09 1万+
------------------------------------------------------------------------------------------------------ Linux下使用TCP的keepalive tcp_keepalive_time     一个连接需要TCP开始发送keepalive探测数据包之前的空闲时间。以秒为单位
oracle TAF
weixin_30378311的博客
11-15 458
转自：Jujay的个人空间 http://blog.itpub.net/26277071/viewspace-710931/ Oracle RAC Failove 之一：Client-Side Connect Time Failover1.定义Client-Side Connect Time Failover是指：如果客户端tnsname.ora中配置了多个地址，用户发送连接请求时，会...
如何合理的设置线程池参数：Oracle官方没有参考值，这本书给出了建议
Hanko的专栏
04-21 912
Oracle 官方并没有给出线程池 corePoolSize 的具体参考值，因为这个值的大小应该根据实际业务场景和系统资源情况来进行优化调整。不同的业务场景和系统资源状况可能需要不同的 corePoolSize 设置。 在《Java并发编程实战》一书中，作者 Brian Goetz 等人指出，线程池的规模应该根据任务类型和计算密集度来确定，对于 CPU 密集型任务，应该将核心线程数设置为处理器核心数加 1 或者 2；对于 I/O 密集型任务，可以适当增加核心线程数以利用空闲的 CPU 时间。
java keepalive,如何通过httpclient在Java中设置TCP Keep Alive
最新发布
05-27
在Java中使用HttpClient设置TCP Keep Alive可以通过以下代码实现： ```java HttpClient client = HttpClientBuilder.create().build(); HttpHost target = new HttpHost("example.com", 80, "http"); HttpRequest ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值