When working with Spring Tool Suite (STS) to develop and redeploy applications, you may encounter an issue where port 8080 is already taken, preventing your application from launching successfully. Understanding why this happens and how to resolve it is crucial for efficient development. This article explores the technical aspects of this issue and provides strategies for resolving it.

What is Port 8080?

Port 8080 is a widely used port in web and application development. It is a non-standard port commonly used by developers as an alternative to the default HTTP port, 80. Applications often use port 8080 for various services, including web servers, application servers, and REST API endpoints.

Why is Port 8080 Already Taken?

Port 8080 may be occupied by:

• A Previously Running Instance of Your Application: In development, a common scenario is failing to stop a previously running instance of the application properly.
• Other Applications or Services: Other services installed on your machine, such as Tomcat, Jenkins, or even another Spring Boot application, might be using the port.
• Zombie Processes: Processes that didn’t terminate correctly may continue to occupy the port.

Identifying the Culprit

Using Command Line Tools

• On Windows: Use the netstat command to find the process running on port 8080. Run the command prompt as an administrator and execute:

  netstat -ano | findstr :8080

This command returns a list of processes with their IDs (PID) bound to port 8080. Use Task Manager to locate these PIDs and identify the applications.

• On Linux/MacOS: Use the lsof utility to check which process is using the port:

  sudo lsof -i :8080

The output provides details about the process, including the PID and the command name.

Resolving Port Conflicts

Once the offending process is identified, you can take the following steps to resolve the conflict:

Terminating the Process

1. Windows: Use Task Manager to end the process or use the command line:

   taskkill /PID <pid> /F

1. Linux/MacOS: Use the kill command:

   sudo kill -9 <pid>

Changing the Application Port

Modify the application.properties or application.yml file of your Spring Boot application to use a different port:

• Using application.properties:

  server.port=9090

• Using application.yml:

  server:
    port: 9090

Configuring STS to Avoid Conflicts

1. Workspace Settings: Ensure that your STS workspace settings do not have configurations that automatically start services on port 8080.
2. Embedded Server Settings: If your Spring Boot application uses an embedded server like Tomcat, customize the port effectively to prevent clashes.

Best Practices

To avoid encountering the "Port 8080 already taken" issue frequently, incorporate these best practices:

Conclusion

The conflict of port 8080 can be a common hurdle in the development lifecycle, especially when working with Spring Boot applications in Spring Tool Suite. Understanding the technical reasons behind the conflict and applying systematic solutions can save time and enhance productivity. Efficiently managing your development environment and ensuring proper cleanup procedures can help minimize these conflicts in the future.