Time：12-10
CodePudding user response:
someone,,,,
your TCP port is occupied by a person, there are several possible, (1) occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot,
Quote: actually I am the true temperament reference 4 floor response: your TCP port is occupied by a person, there are several possible, (1) occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot, I had fewer than 8080 CMD search port,,,
Quote: refer to the fifth floor qq_46152955 reply: Quote: reference reply: actually I'm true colors, 4/f your TCP port is occupied by a person, there are several possible, 1. Occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot, I had fewer than 8080 CMD search port,,, I all dizzy, your own program is written to port 8998, search for port 8080, it's not running tomcat, write their own procedures need to be able to read the first, you should be the second run the program, I said your program is a server-side program, for the first time you run time didn't receive client information, so has been waiting for, the second time you run when the port is already in the first run the program takes up so error, first you understand what the socket, and then understand this program USES,
Quote: reference reply: actually I'm true colors, 4/f your TCP port is occupied by a person, there are several possible, 1. Occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot, I had fewer than 8080 CMD search port,,,
your TCP port is occupied by a person, there are several possible, 1. Occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot,
Quote: refer to 7th floor qq_39936465 response: Quote: refer to the 5 floor qq_46152955 response: Quote: reference reply: actually I'm true colors, 4/f your TCP port is occupied by a person, there are several possible, 1. Occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot, I had fewer than 8080 CMD search port,,, I all dizzy, your own program is written to port 8998, search for port 8080, it's not running tomcat, write their own procedures need to be able to read the first, you should be the second run the program, I said your program is a server-side program, for the first time you run time didn't receive client information, so has been waiting for, the second time you run when the port is already in the first run the program takes up so error, first you understand what the socket, and then understand this program USES, Well how junction post
Quote: refer to the 5 floor qq_46152955 response: Quote: reference reply: actually I'm true colors, 4/f your TCP port is occupied by a person, there are several possible, 1. Occupied by other programs such as 8080, so you just start tomcat this port occupied the first, you can't listen again, 2. Could you program run die, background processes not terminated, so ports occupied, restart your computer, or find the process in the process to kill, The simplest solution, you have to do is to change the port, literally in a 9090 this, for example, Remember that the knot, I had fewer than 8080 CMD search port,,, I all dizzy, your own program is written to port 8998, search for port 8080, it's not running tomcat, write their own procedures need to be able to read the first, you should be the second run the program, I said your program is a server-side program, for the first time you run time didn't receive client information, so has been waiting for, the second time you run when the port is already in the first run the program takes up so error, first you understand what the socket, and then understand this program USES,
Page link：https//www.codepudding.com/Backend/93459.html
