large freesync monitor

; Path:D:\app\Administrator\diag\rdbms\orcl\orcl\trace\alert_orcl.log A large number of errors are found by viewing the log:tns-12537: TNS: Connection off 12560 0 0 0By Baidu error keyword "Tns-12537:tns: Connection Close", found an article:http://blog.itpub.net/23169974/viewspace-1067401/This article describes the problem that the Listener.log log file is too large

servers, the parameters of the last few lines can be a good way to reduce the number of time_wait sockets, but for Squid, the effect is not small. This parameter controls the maximum number of time_wait sockets, preventing squid servers from being dragged to death by a large number of time_wait sockets.Tuning is complete, then press to see the effect of it.# Netstat-n | awk '/^tcp/{++y[$NF]} END {for (w in y) Print W, Y[w]} ' established 968Is

of connections is too largeHow to resolve the request after the end of the still large number of established not released preliminary inference tomcat server recycling session There was a problem, this is usually the server's timeout settings are linked. View Tomcat the configuration file Server.xmlConnectorPort= "8080"Protocol= "http/1.1"ConnectionTimeout= "20000"Redirectport= "8443"uriencoding= "UTF-8" />*****Check configuration 20000

Problem Description: Without considering the system load, CPU, memory, etc., netstat monitors a large number of established connections and time_wait connections. # Netstat-n | awk '/^tcp/{++y[$NF]} end {to (w in y) Print W, y[w]} ' close_wait 348 established 1240 time_wait Monitor the link port between Apache and Tomcat #netstat-N | grep 8009 | Wc-l Question 1: How to solve a lot of time_w

Problem Description: Without considering the system load, CPU, memory, etc., netstat monitors a large number of established connections and time_wait connections. # Netstat-n | awk '/^tcp/{++y[$NF]} end {to (w in y) Print W, y[w]} ' close_wait 348 established 1240 time_wait Monitor the link port between Apache and Tomcat #netstat-N | grep 8009 | Wc-l Question 1: How to solve a lot of time

loss. Then I use the root user in the/root directory. Bash_history someone using iptables-l this command to view the firewall rules, I finally boss told me:Remember: Do not use iptables instructions (such as IPTABLES-NL) to view the current status while the firewall is down! Because this causes the firewall to be started, and the rule is empty. Although there is no blocking effect, all connection states are logged, wasting resources and impacting performance and possibly causing the firewall to

loss. Then I use the root user in the/root directory. Bash_history someone using iptables-l this command to view the firewall rules, I finally boss told me:Remember: Do not use iptables instructions (such as IPTABLES-NL) to view the current status while the firewall is down! Because this causes the firewall to be started, and the rule is empty. Although there is no blocking effect, all connection states are logged, wasting resources and impacting performance and possibly causing the firewall to