Several ports (8005, 8080, 8009) required by Tomcat Server at localhost are already in use

JavaEclipseTomcat

Java Problem Overview


I'm getting the following error when I try to run a simple JSP program on Tomcat in Eclipse.

> Several ports (8005, 8080, 8009) required by Tomcat v6.0 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).

How is this caused and how can I solve it?

Java Solutions


Solution 1 - Java

You've another instance of Tomcat already running. You can confirm this by going to http://localhost:8080 in your webbrowser and check if you get the Tomcat default home page or a Tomcat-specific 404 error page. Both are equally valid evidence that Tomcat runs fine; if it didn't, then you would have gotten a browser specific HTTP connection timeout error message.

You need to shutdown it. Go to /bin subfolder of the Tomcat installation folder and execute the shutdown.bat (Windows) or shutdown.sh (Unix) script. If in vain, close Eclipse and then open the task manager and kill all java and/or javaw processes.

Or if you actually installed it as a Windows service for some reason (this is namely intented for production and is unhelpful when you're just developing), open the services manager (Start > Run > services.msc) and stop the Tomcat service. If necessary, uninstall the Windows service altogether. For development, just the ZIP file is sufficient.

Or if your actual intent is to run two instances of Tomcat simultaneously, then you have to configure the second instance to listen on different ports. Consult the Tomcat documentation for more detail.

Solution 2 - Java

kill $(ps -aef | grep java | grep apache | awk '{print $2}')
  • no need to restart Eclipse
  • if you get the above error, just enter this line in terminal
  • again start the tomcat in Eclipse.
  • works only in Linux based system ( Ubuntu ..etc )

Solution 3 - Java

If you are running on windows try this in the command line prompt:

netstat -ano

This will show all ports in use and the process id PID # of the process that is using that port. Then Ctrl+Alt+Del and open Task Manager to see which process is that.

You can then choose either to close/stop it or configure your server to use another port. To check if the new choosen port (let's say 8010) is available do this:

netstat -ano | grep 8010

If it does not return any lines then you are fine.

To change the port go to the Server view, open server.xml and change the port there. Mine has this entry:

Connector port="8010" protocol="AJP/1.3" redirectPort="8443"

Solution 4 - Java

If you are on mac environment, here is what I did.

Find the process id running on this port from terminal, eg, 8080:

lsof -i :8080

and kill it:

kill -9 <PID>  

Example:

You may see following result:

MacSys:bin krunal.$ lsof -i :8080

COMMAND   PID     USER   FD   TYPE     DEVICE  SIZE/OFF   NODE  NAME
java     21347   krunal  52u  IPv6      XXX      0t0      TCP  *:http-xxx (LISTEN)

and kill it: (kill -9 21347)

Solution 5 - Java

Steps to free port which is already used to run tomcat server in Eclipse

For example , suppose 8080 port is used , we need to make free 8080 to run tomcat

Step 1:

C:\Users\username>netstat -o -n -a | findstr 0.0:8080

TCP 0.0.0.0:3000 0.0.0.0:0 LISTENING 3116

Now , we can see that LISTENING port is 3116 for 8080 ,

We need to kill 3116 now

Step 2:-

C:\Users\username>taskkill /F /PID 3116

Step 3: Go to Eclipse and start Server , it will run

Solution 6 - Java

If you use Eclipse then double click on servers and double click on tomcat server then one file will open. In that file change HTTP port to some other port number and save(Ctrl+S) then again start the server.

Solution 7 - Java

If Eclipse says

> Several ports (8005, 8080, 8009) required by Tomcat v6.0 Server at localhost are already in use

This error comes because tomcat may be running in background so first stop that server..follow the below details.

Solution is:

  1. Open the "console" view (window->show view->Console)
  2. Then stop the tomcat server.
  3. Then open the "server" view and start the server it will work.

Thanks!

Solution 8 - Java

I have no another instance of Tomcat running ad no other process using "Tomcat port" (in my case, the 8088 port). Eclipse send the same message on starting Tomcat:

....The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s).

I solve the problem in this way:

  • go to bin of tomcat by prompt
  • launch startup.bat
  • launch shutdown.bat
  • start tomcat by Eclipse

Solution 9 - Java

What I did after reading all the suggested answer and as I know my port was already in use. I double clicked on Tomcat under the Servers tab in eclipse and it opened overview information and then find port information. Just changed conflicting port as mine was 8009 port (error mentioned during starting the server). I have changed it to 8008 and it works fine. Give a try if the changed port would not be in use server will start.

Solution 10 - Java

Step 1: netstat -a -o -n and it will bring up a network list,search for the local address like 127.0.0.1:8080 and note the PID (eq 3624)

C:\>netstat -a -o -n

Step2 : taskkill /F /PID 3624 . Run this command to kill that process.

C:\>taskkill /F /PID 3624

link to post

Solution 11 - Java

On Windows use command for stopping the already running tomcat instance and try running it again in eclipse, it may work.

net stop tomcat7 

Or you can change the port in server's XML if you just want to run on some other ports.

Solution 12 - Java

Easy way to solve your problem:

The server may already be running in another process, or a system process may be using the port. In order to kill that port, do the following:

  1. Download TCPView(only 285kb) from following link.

    <http://technet.microsoft.com/en-in/sysinternals/bb897437.aspx>

  2. Extract folder and start TCPView application.

  3. Right click on java.exe(because 8009,8005 ports are commonly used by java process) and select End Process option.

this would stop another process easily..

NOTE: Running TOMCATPATH/bin/shutdown.bat may not shutdown Tomcat when it contains some demon or unmanaged threads. In such cases TCPView works fine without any issues.

Solution 13 - Java

I checked all the answers but informing only to kill PID.

In case if you have terminal access shared by all it will not help or maybe you do not have permission to kill PID.

In this case what you can do is:

Double click on server

Go to Overview and change ports in Ports like this:

enter image description here

Solution 14 - Java

If you are in Java EE prospective in Eclipse and trying to start the Tomcat Server in Eclipse in debug mode, then you will get such errors. You must switch to debug prospective in Eclipse. I have solved my problem like this.

Solution 15 - Java

Sometimes if the ports are not freed even after attempting shutdown.bat what @BalusC suggested,you can kill the javaw process. Do following steps :

  1. Click on Start Menu and open "Windows powershell"
  2. Right click before opening and select "Run as administrator"
  3. Enter command ps. You may see a image as follows : Powershell showing current proesses running
  1. See the process number of process "javaw".The process number is the rightmost number in the columns, I have highlighted in the image process number of javaw for example.

  2. Enter command kill . javaw is killed and now you must be able to run the program.

Solution 16 - Java

Here's one more option to try if none of the efforts above helped. You might be using Eclipse from a Shared Drive (for eg, H:). If so, move/copy it the entire Eclipse directory to C: and try again.

My Eclipse could not open ports for Tomcat server (with the above error), nor even connect to internet. I also tried another Tomcat plugin (Sysdeo) which failed to open the ports too.

These are the options I tried:

Check and Kill Other Tomcat Instances

  • In command prompt, netstat -ano and check if any other processes are using the conflicted ports.
  • Find the PID and kill it
  • Try starting the server again.

Change Tomcat Ports in Eclipse

  • In Eclipse Server tab, double click the Tomcat instance. This will open the configuration tab.
  • Under Ports, change the port numbers. (for eg, 18080).

Kill java.exe and javaw

See my other answer for Eclipse not connecting to Internet (https://stackoverflow.com/a/37246087/4212710).

Solution 17 - Java

For windows users:

Go to Task Manager directly with CTRL+SHIFT+ESC key combination.

Kill the "java.exe" processes by right clicking and selecting "End Task".

Solution 18 - Java

The simpler fix that works for me is deleting my current deployed webapps from tomcat through the "Server" tab. Once I remove them the problem goes away. Simply re-deploy your project by going on Run As > Run on Server.

Solution 19 - Java

The problem often arises when Apache Tomcat fails to terminate, properly, even though a shutdown instruction was sent. In my case, using Tomcat 8, this happens with annoying regularity. Luckily, you can use Windows PowerShell and the netstat command to create a simple script to kill the process.

The following PowerShell script will parse the output from netstat to find any process that is listening on 127.0.0.1:8005, extract its PID and then kill that process:

netstat -a -o -n `
 | select -skip 4 `
 | % {$a = $_ -split ' {3,}'; New-Object 'PSObject' -Property @{Original=$_;Fields=$a}} `
 | ? {$_.Fields[1] -match '127\.0\.0\.1\:8005$'} `
 | % {Write-Host "Killing PID" $_.Fields[4] "..."; taskkill /F /PID $_.Fields[4] }

If your server.xml configures Tomcat to use a different port or IP, edit the regular expression on the script's fourth line accordingly.

Finally, I should point out that the situation is better on Linux because you can instruct Tomcat to save its PID to a file at startup-time and use a switch to force the shutdown, later - the shutdown script for 'nix systems already features the ability to kill the process and the sleuth-work with netstat is not required.

Solution 20 - Java

If the above issue occurs in Windows 7 or 10 based OS, the problem occurs because Tomcat is running as Windows Service. To stop Tomcat running as Windows Services, Open Windows Control Panel. Find the service "Apache Tomcat" and Stop it. The Another way is to kill the process running on port 8080 using cmd.

Open cmd running it as administrator.

  1. C:\users\username>netstat -o -n -a|findstr 0.0:8080
  2. TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 2160.
  3. The above 2160 is process id of process running on port 8080 and kill that process using the following command
    C:\users\username>taskkill /F /PID 2160
  4. Go to IDE and start Server, it will run

Solution 21 - Java

It may be because you are not stopping your tomcat service properly. To do that, Open your task manager there you can see a javaw.exe service. First stop that service. Now restart your tomcat it works fine.

Solution 22 - Java

In my case, it was giving me the error: Port 8005 required by Tomcat v8.0 Server at localhost is already in use

I changed 8005 port in apache-tomcat-8.0.39\conf\server.xml but changes were not getting reflected. Then I did these changes from eclipse. by double clicking server and modifying the port from 8005 to 8006 and it works. enter image description here

Before putting 8006 I checked in windows shell if this port is available or not. By executing following command:

netstat -a -o -n | findstr 8006

Solution 23 - Java

I face the same problem and after searching the answer as shown below:

  1. open Monitor Tomcat as shown below: enter image description here

  2. Simply press stop as shown in below picure:

enter image description here

Finally it works with me after many trials and suggested solutions.

Best Regards, Kerelos Mikhail

Solution 24 - Java

Refer to the following blog "how to kill tomcat without have to restart your computer"

http://stanicblog.blogspot.fr/2012/01/how-to-kill-apache-tomcat-without.html

Hope this will help someone in the future.

Solution 25 - Java

On Eclipse make a raw delete of Tomcat configuration folder under project "Servers". I tried it as last hope and it worked.

Solution 26 - Java

In case of windows, I experienced a new stuff... stopping tomcat from /bin folder will immediately not releasing the port 8080. It takes around 5-10 mins to release the port. After 10 mins again if i try to run my project Run-> Run on server .. it allows to run.

I'm unsure whether my understanding is correct!

Solution 27 - Java

>Several ports (8005, 8080, 8009) required by Tomcat vX.X Server at localhost are already in use

To check whether another instance of Tomcat already running or some other process is using the ports you can use:

>netstat -b -a in command prompt for windows. This lists the ports in use and gives you the executable that's using each one. You need to be in the admin group to do this.

You might get something like this:

>TCP 192.168.0.1:8009 192.168.0.1:0 LISTENING 196 [Tomcat7.exe] > >TCP 192.168.0.1:8080 192.168.0.1:0 LISTENING 196 [Tomcat7.exe] > >TCP 192.168.0.1:8005 192.168.0.1:0 LISTENING 196 [Tomcat7.exe]

Open task manager Ctrl+Shift+Esc, and kill Tomcat7.exe or any other process using these ports.

Solution 28 - Java

It occurs when others in the project are also using the same port numbers as you are using! double click tomcat server, change port numbers to anything 8585 or whatever. The code will now begin to run!

Solution 29 - Java

How to kill a windows service using PID -

  1. open command prompt and type netstat -ano
  2. find the PID of the ports which are in used, in this case, it will be 8080, 8005,8009. Let's say PID of these ports are 5760.
  3. Now Type taskkill /f /pid 5760
  4. it will close the PID and ports will be available for use. Now you can start tomcat as normal by Windows services or by eclipse itself.

Thanks

kill a Windows service that's stuck on stopping or starting

Solution 30 - Java

Your Tomcat is probably running already. That's why you have got an error. I've had the same problem before. I solved it very simply:

  1. Restart your computer
  2. Open Eclipse
  3. Run your Tomcat

That's all.

Solution 31 - Java

In windows OS do right click on task bar-->start task manager-->process then check java.exe or javaw is running if it is running,then click on it and do end process then restart your tom cat server.

  1. some times skype will occupy port 80 in that case change the skype settings and put 81 for skype or change tomcat configuration.

Solution 32 - Java

Don't need to close your eclipse IDE.Your Tomcat is probably running already. That's why you have got an error.

open tomcat directory >> bin >> from command terminal (in my case is tomcat9)

Enter command

./shutdown.sh

it will close your running tomcat

enter image description here

Solution 33 - Java

Easiest solution

Single line command for killing multiple ports:

kill $(lsof -t -i:8005,8080,8009) 

8005, 8080 and 8009 are the ports to be freed.

Alternatively, you can try sudo kill sudo lsof -t -i:8005 in linux.

Solution 34 - Java

All of above do not work for me.

What I found was click the Details button. enter image description here

Then following the https://stackoverflow.com/questions/7239613/multiple-contexts-with-the-same-path-error-running-web-service-in-eclipse-using

Removed the duplicated line then I got an another error.

The server cannot be started because one or more of the ports are invalid. Open the server editor and correct the invalid ports.

Following https://stackoverflow.com/questions/59471438/cant-start-tomcatv9-0-in-eclipse

Then it works.

Solution 35 - Java

Macbook solution:

Step 1: stop the server running Java :

Open Activity Monitor by going to Applications > Utilities > Activity Monitor. Or simple press CMD + Spacebar and start typing Activity Monitor. Look for process running Java and kill it by giving the following command in Terminal

kill -STOP <PID> 

where PID is the process ID of the Java process as displayed in the Activity Monitor. Do it a couple of times and close and reopen Activity Monitor to check Java isn't running.

Step 2: change the port :

right-click on the server in Eclipse and click 'Open'. Change port number from 8080 to 8081 or something greater in value.

This should hopefully start your server.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionelleView Question on Stackoverflow
Solution 1 - JavaBalusCView Answer on Stackoverflow
Solution 2 - JavaShanView Answer on Stackoverflow
Solution 3 - JavaMauView Answer on Stackoverflow
Solution 4 - JavaTimelessView Answer on Stackoverflow
Solution 5 - JavaSachindra N. PandeyView Answer on Stackoverflow
Solution 6 - JavaabcView Answer on Stackoverflow
Solution 7 - JavaAshu PhaugatView Answer on Stackoverflow
Solution 8 - JavagiocoritoView Answer on Stackoverflow
Solution 9 - JavaDeVilCry2MEView Answer on Stackoverflow
Solution 10 - JavaSandeep BhardwajView Answer on Stackoverflow
Solution 11 - JavaGaurangaView Answer on Stackoverflow
Solution 12 - JavashivadarshanView Answer on Stackoverflow
Solution 13 - Javav8-EView Answer on Stackoverflow
Solution 14 - JavaJitendraView Answer on Stackoverflow
Solution 15 - JavaTiny JaguarView Answer on Stackoverflow
Solution 16 - JavatypoerrprView Answer on Stackoverflow
Solution 17 - JavaArif AcarView Answer on Stackoverflow
Solution 18 - JavaFelipe LeãoView Answer on Stackoverflow
Solution 19 - JavaXharlieView Answer on Stackoverflow
Solution 20 - JavaShreeram ReddyView Answer on Stackoverflow
Solution 21 - JavaRam ThotaView Answer on Stackoverflow
Solution 22 - JavaTahirView Answer on Stackoverflow
Solution 23 - JavaKerelosView Answer on Stackoverflow
Solution 24 - JavaEdmund NgView Answer on Stackoverflow
Solution 25 - JavagiocoritoView Answer on Stackoverflow
Solution 26 - JavaLaxmanView Answer on Stackoverflow
Solution 27 - JavaZeeshanView Answer on Stackoverflow
Solution 28 - JavaShivendraView Answer on Stackoverflow
Solution 29 - JavaPankaj BarnwalView Answer on Stackoverflow
Solution 30 - JavaPurgoufrView Answer on Stackoverflow
Solution 31 - JavaVasundharaView Answer on Stackoverflow
Solution 32 - JavaKamranView Answer on Stackoverflow
Solution 33 - JavaAbhijith SasikumarView Answer on Stackoverflow
Solution 34 - JavaHelloView Answer on Stackoverflow
Solution 35 - JavakushView Answer on Stackoverflow