JDBC连上来的session断线后如何立刻kill掉?

d.c.b.a

通过v$process和v$session可以找SPID来的,然后杀吧

fireyou

最初由 lovexueer 发布
[B]用这个吧，PROCESSVIEW
另外你可以试试weijsh兄的方法，修改sqlnet，这个我没用过。 [/B]

processview我找了好久都没找到，能传上来吗

husthxd

Key Word :
Dead Connection Detection

wish the following document can help u:

1.
Dead Connection Detection (DCD) is a feature of SQL*Net 2.1 and later, including
Net8. It detects when a partner in a SQL*Net V2 client/server or server/server
connection has terminated unexpectedly, and releases the resources associated
with it.

DCD is intended primarily for environments in which clients power down their
systems without disconnecting from their Oracle sessions, a problem characteristic
of networks with PC clients.

DCD is initiated on the server when a connection is established. At this
time SQL*Net reads the SQL*Net parameter files and sets a timer to generate an
alarm. The timer interval is set by providing a non-zero value in minutes for
the SQLNET.EXPIRE_TIME parameter in the sqlnet.ora file.

2.
On most OS'es (even more recent versions of Windows) if a process exits
abnormally or is killed by an administrator, the OS will still gracefully
clean up resources associated with that process including the network
connection(s). It will tell the server on the other end that it is closing
the network connection. DCD is still useful for times when there are problems
with the physical network (e.g. ethernet cable falls off the machine) or if the
OS kernel panics and crashes (e.g. blue screen of death) before it can close
the network connections. It may have another side benefit with certain load
balancing hardware, that may prematurely abort connections it thinks have been
idle too long, by sending a dummy packet to the client periodically.

Under no circumstances should you rely 100% on Dead Connection Detection.
It was developed to handle clients that have abnormally exited. Clients
should always exit their applications gracefully. It is the responsibility of
the application developer to make this possible. DCD is intended only to clean
up after abnormal events.

DCD is much more resource-intensive than similar mechanisms at the protocol
level, so if you depend on DCD to clean up all dead processes, that will put
an undue load on the server.

Clearly it is advantageous to exit applications cleanly in the first place.

weijsh

最初由 CUTE_ORACLE 发布
[B]

这样的话就是客户断与DB直接通信了!
觉得,在sqlnet.ora 设
SQLNET.EXPIRE_TIME=10 方法是应该可以的.
可能时间太长..你试试..
SQLNET.EXPIRE_TIME=0 [/B]

java写的exe是通过jdbc连接数据库，另外还有web服务是通过weblogic连上来的，SQLNET.EXPIRE_TIME=0会不会影响到weblogic？ 如果影响的话不是隔几秒就要重新登录系统？

fireyou

最初由 weijsh 发布
[B]

java写的exe是通过jdbc连接数据库，另外还有web服务是通过weblogic连上来的，SQLNET.EXPIRE_TIME=0会不会影响到weblogic？ 如果影响的话不是隔几秒就要重新登录系统？ [/B]

不管对weblogic有没有影响，你都要找个环境测试一下再用到在线系统上啊，别人如果说没有影响，万一用了有影响呢？

lovexueer

husthxd贴子说的很清楚。
DCD给服务器造成了不必要的负担。
通过OS kill方法，资源确实release的好

processview偶也没有找到，看下边这个是否有用。
http://www.onlinedown.net/soft/1409.htm

husthxd

最初由 weijsh 发布
[B]

java写的exe是通过jdbc连接数据库，另外还有web服务是通过weblogic连上来的，SQLNET.EXPIRE_TIME=0会不会影响到weblogic？ 如果影响的话不是隔几秒就要重新登录系统？ [/B]

SQLNET.EXPIRE_TIME是用来监测DCD的.不会对其他正常的数据库连接有影响了.
windows平台下用orakill清除thread,unix平台下用kill -9清除.
http://blog.itpub.net/post/11/20675

weijsh

多谢各位，SQLNET.EXPIRE_TIME=0 这方法可行，目前还没发现会对其它应用造成负面影响

weijsh

测试了一天，设置SQLNET.EXPIRE_TIME=0  
系统好象并不会在断线后立刻把session kill掉,总要隔几秒或几十秒几分种不等

husthxd

最初由 weijsh 发布
[B]测试了一天，设置SQLNET.EXPIRE_TIME=0  
系统好象并不会在断线后立刻把session kill掉,总要隔几秒或几十秒几分种不等 [/B]

这个除了跟oracle有关之外跟os应该也有点关系.
只是猜测......