Linux 80 Port-occupied solution for Tomcat

Failure: Website cannot access analysis: Netstat-an See a large number of 80 port process zombie, restart Tomcat.tomcat failed to start, the webpage still cannot open. Stop Tomcat process shutdown.sh, stop Tomcat after Telnet 127.0.0.1 80, found that 80 ports are still available. Netstat-an|grep 80 View found there are many 80 port processes inside, using the kill PID command to terminate the process, useless. Use lsof-i: 80|grep-v "PID" |awk ' {print ' kill-9 ', ' $ $ ' command after all 80-port processes are removed. Restart Tomcat and the system is functioning properly. Why, however, it is necessary to analyze why Tomcat cannot shut down the 80-port process when it shuts down.

[Email protected] bin]# Netstat-an |grep 80
TCP 0 0:: ffff:127.0.0.1:8005:::* LIST
En
TCP 0 0::: 8009:::* LIST
En
TCP 0 0::: +:::* LIST
En
TCP 0 0::: 8080:::* LIST
En
TCP 0 0:: ffff:172.16.1.153:80:: ffff:202.160.179.12:36057 time
_wait
TCP 0 0:: ffff:172.16.1.153:80:: ffff:202.160.178.15:39176 time
_wait
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:55001 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:3516 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:55037 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:3518 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:61.135.162.208:57893 time
_wait
TCP 0 0:: ffff:172.16.1.153:80:: ffff:210.72.4.122:39196 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:59.32.124.136:22529 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:55222 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:218.20.57.173:3510 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:59.32.124.136:22530 ESTA
Blished
TCP 0 0:: ffff:172.16.1.153:80:: ffff:210.72.4.122:39198 ESTA
Blished
UNIX 3 [] STREAM CONNECTED 6880/tmp/. X11-unix/x0
# Lsof-i: 80|grep-v "PID" |awk ' {print ' kill-9 ', $ $} ' |sh
The above script can clear the 80 port process

In fact, Windows 8 is a bold step in hosting the transformation vision of Microsoft and representing the mobility of Windows systems. But obviously, the inadequacy of many details has led to its failure, forcing Microsoft to improve on these aspects in Windows 10.

Failure Gene One: Start menu disappears

Since Windows 95, the Start menu has become an iconic design of the Windows system, gradually accepted and used by users, it can quickly open other applications and interfaces in the form of non-full-screen, without changing the current interface, enabling a very convenient and fast operation experience. When Windows 8 decides to change it to modern ui/traditional desktop's jump function, Windows 8 is doomed to fail.

Most users have to get used to this new design, but it is a nightmare for users who simply use traditional desktops, and the operation is much less efficient. While Microsoft offers features such as booting into a traditional desktop in Windows 8.1, the effect is still limited.

Resources:

http://www.douban.com/note/484043213/
http://www.douban.com/note/484043756/
http://www.douban.com/note/484044190/
http://www.douban.com/note/484044510/
http://www.douban.com/note/470017824/
http://www.douban.com/note/473574252/
http://www.douban.com/note/473999945/
http://www.douban.com/note/473573575/

Linux 80 Port-occupied solution for Tomcat