Port 8080 already being used by "SYSTEM"

Question

apache tomcat is not working on port 8080. I tried to figure out what program is running on port 8080 with the netstat command

**C:\Users\SGaiks>netstat -aon | find ":8080"

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING       4

  TCP    [::]:8080              [::]:0                 LISTENING       4**

the program having PID 4 is running on port 8080, so I checked what program is having PID 4 in the task manager and I get SYSTEM (here are the details since I cannot post screenshots)

Name :- SYSTEM
PID :- 4
Status :- Running
Username:- SYSTEM
CPU :- 01
Memory :- 88k
Description :- NT Kernal & System

what does this actually mean? how do i disable the program that is using port 8080?

I have seen many similar questions asked but that didn't help.

(dont know if doing this is right) --> I also changed the port to some random port (localhost:2200) to run tomcat on localhost and it successfully runs. but I want it to run on localhost:8080

Answer 1

Try to open a browser and go to http://localhost:8080. If you're lucky, you have another server running and it'll serve a page. Otherwise, I'll try to dig more to help you.

EDIT 1 : The server seems to answer (even if the requested resource wasn't found), so you should have another server running. Take a look at http://support.microsoft.com/kb/284285 for troubleshooting HTTP connexion problems, and give us the result

Answer 2

In my case netstat was unable to show the owning process even from an elevated command prompt.

As it turns out, the port was used by OracleXETNSListener which was running under Local System.

Answer 3

Issue was found: For some reason windows Media Server was running in IIS Server stoped. Port 8080 is now OK and available to my app.

Answer 4

For anyone else running into this issue try running netsh http show servicestate and looking at registered URLs or Logging information.....my issue was I had a WCF service running as a windows service. Original Credit - pazadev

Answer 5

I simply Stopped IIS Manager and it worked which freed 8080 port to be picked by IISExpress