Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
The Tomcat java.net.BindException: Address Already in Use Error in Java
Last updated: January 24, 2024
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Mocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Explore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Modern software architecture is often broken. Slow delivery leads to missed opportunities, innovation is stalled due to architectural complexities, and engineering resources are exceedingly expensive.
Orkes is the leading workflow orchestration platform built to enable teams to transform the way they develop, connect, and deploy applications, microservices, AI agents, and more.
With Orkes Conductor managed through Orkes Cloud, developers can focus on building mission critical applications without worrying about infrastructure maintenance to meet goals and, simply put, taking new products live faster and reducing total cost of ownership.
Try a 14-Day Free Trial of Orkes Conductor today.
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely — and automatically — with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. That’s where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions — one for newcomers and one for experienced users. You’ll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
Yes, we're now running our Black Friday Sale. All Access and Pro are 33% off until 2nd December, 2025:
1. Overview
In this quick tutorial, we’ll look at what causes the common java.net.BindingException Error: Address already in Use error and how we can deal with it.
2. When Does the Error Occur?
As we know, the Apache Tomcat server, by default, uses the 8080 port.
Port numbers range from 0 to 65535, however, a port can only be occupied by a single application at any time.
The exception states that the application is trying to use a port that’s already taken by some other process, or we didn’t stop the Tomcat server properly.
3. Diagnosing
To solve this error, we can either kill the service taking that port or can change our web server to run on another port.
3.1. Discovering the Conflict
In this case, we need to find out which application is using the port.
The netstat command can be used for discovering current TCP/IP connections.
Below are the commands that can be used to find and kill the process in different environments.
On Windows, the last column of output will give us the process id of the service currently running on 8080:
netstat -ano | find "8080"Output:
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 21376
Here, 21376 is the process id of the process which is listening on port 8080.
On Unix/Linux Environment:
netstat -pant | grep "8080"Output:
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 21376
Same as Windows output. Here, 21376 is the process id of the process which is listening on port 8080.
On Mac OS X:
lsof -t -i :8080Output:
21376It will display the PID only.
3.2. Running Server on Another Port
If we know what process is running, why it’s running and that it needs to be running on that port, we can change the port that our server application is attempting to run on.
To change the Tomcat port, we need to edit the server.xml file. To do this:
- Open tomcat/conf folder
- edit server.xml
- replace the connector port with the new port
- restart tomcat server
The server.xml file looks like this:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000" redirectPort="8443" />Now Tomcat will run on the customized port.
3.3. Killing the Running Service
To stop the running process, we can use the kill command.
Using the process ID that we found in 3.1., we’ll require different commands depending on the Operating System we’re running.
On Windows environment:
taskkill /F /PID 21376On Unix/Linux environment:
kill - 21376Mac OS X environment:
kill -9 213764. Conclusion
As mentioned at the beginning of the article, java.net.BindingException is a prevalent but easily resolved error.
The main difficulty is in finding the conflicting service using the port with the netstat terminal application then deciding the appropriate course of action.
Once discovered, the fix is easy.
