DCD (dead connection detection) on Linux
From: Hameed, Amir <Amir.Hameed_at_xerox.com>
Date: Thu, 31 Oct 2013 00:50:07 +0000
Message-ID: <AF02C941134B1A4AB5F61A726D08DCED0DED7BD8_at_USA7109MB012.na.xerox.net>
Folks,
RDBMS - 11.2.0.3
Linux - RHEL 6/U4
Oracle E-Business Suite R12
I have noticed that DCD is not working quickly enough in my database even if I set "SQLNET.EXPIRE_TIME= 1" on the database server. If I crash my Linux host running the http server while I have connections established to the application, I can see that dead connections in the database corresponding to the application connections take somewhere from 12-15 minutes to get cleaned up. I can see that the TCP keep-alive parameters on Linux are set as shown below:
Date: Thu, 31 Oct 2013 00:50:07 +0000
Message-ID: <AF02C941134B1A4AB5F61A726D08DCED0DED7BD8_at_USA7109MB012.na.xerox.net>
Folks,
RDBMS - 11.2.0.3
Linux - RHEL 6/U4
Oracle E-Business Suite R12
I have noticed that DCD is not working quickly enough in my database even if I set "SQLNET.EXPIRE_TIME= 1" on the database server. If I crash my Linux host running the http server while I have connections established to the application, I can see that dead connections in the database corresponding to the application connections take somewhere from 12-15 minutes to get cleaned up. I can see that the TCP keep-alive parameters on Linux are set as shown below:
cat /proc/sys/net/ipv4/tcp_keepalive_time
7200
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
75
Does anyone know what are all the parameters that need to be set to allow DCD work within 1-2 minutes?
Thanks,
Amir
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Oct 31 2013 - 01:50:07 CET