Run taskmgr in the command prompt.Port 80 in use by unable to open process with PID 4 This can be done in the Windows command prompt. To determine the executable running as this process ID, you need to use Windows Task Manager. The sample output above indicates that the local port 80 is being used by process ID 2636. Proto Local Address Foreign Address State PID netstat should produce output similar to the example below: C:\Documents and Settings\Administrator>netstat -o
This will output a list of ports, along with the PID (process ID) that has that port open. Follow the instructions for the third-party tool you use to determine what process is using port 80.Īt a Windows command prompt, run the command netstat -o. If you need to determine the port in use on older, unsupported versions of Windows, third-party tools are availalbe online. This guide requires Windows Task Manager and netstat, both of which are availalbe on Windows XP, Windows 2003 and newer versions of Windows. For example, localhost:8080/myApplication/index.a5w When you publish your application, you must include the chosen Server Port in as part of the URL that they access. Specify a port that is not 80, such as 8080. Change the Server Port in the Application Server Control Panel and start the server. If you are running the Development Application Server, changing the port used by the server is the easiest solution. If this happens, you can either use a different port for the Application Server, or you can determine what other program is using the port and stop it. When you attempt to start the Application Server, it will warn you if there is already some other program using the port it is configured to use and it will then abort starting.
The combination of IP address and TCP port is what provides the unique address for your service, so only one process can use a given port at a time.
Network services use TCP ports to "listen" for incoming requests from remote clients and service them.
0 kommentar(er)
