Skip to content

Santhosh Ponnam

Technology Blog

  • Home
  • About
  • Technology
    • Java
    • ORM
  • Privacy Policy
  • Toggle search form
  • hashCode and equals methods in java Java
  • Unique Random ‘N’ digit Number generator Java
  • Fixing Log4j Vulnerability Java
  • HikariCP Configurations – Database Connection Pooling Installations and Configurations
  • HikariCP Connection Pooling for Spring Boot for 1.x version Spring Boot
  • Setting Environment Variables in Windows Java
  • Log4J (RCE) Vulnerability Java
  • Log4j Vulnerability / Version Upgrade to 2.16.0 by Apache Team Java

Windows Commands – kill port number

Posted on March 29, 2020March 29, 2022 By Santhosh Ponnam No Comments on Windows Commands – kill port number

How do I kill the process currently using a port on localhost in Windows?

Step 1: Open up cmd.exe (note: you may need to run it as an administrator, but this isn’t always necessary as long as you are trying to kill a port which is started within your user), then run the below command:

netstat -ano | findstr :<PORTNO> 
Example: netstat -ano | findstr :8080

(Replace <PORT> with the port number you want, but keep the colon)


Step 2: Next, run the following command:

taskkill /PID <PID> /F
Example: taskkill /PID 4664 /F
SUCCESS: The process with PID 4664 has been terminated.

References : https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands

Installations and Configurations, Spring Boot HikariCP Connection Pooling Tags:kill port number, netstat, port number, Windows

Post navigation

Previous Post: Why to have a private constructor?
Next Post: HikariCP Connection Pooling for Spring Boot for 1.x version

Related Posts

  • HikariCP Connection Pooling for Spring Boot for 1.x version Spring Boot
  • HikariCP Configurations – Database Connection Pooling Installations and Configurations
  • Sonar Qube – Code Coverage and Code Quality Tool Installations and Configurations

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Another Log4j Bug – DoS
  • Log4j Vulnerability / Version Upgrade to 2.16.0 by Apache Team
  • Fixing Log4j Vulnerability
  • Log4J (RCE) Vulnerability
  • JPA vs Hibernate – Specification Vs Implementation

Categories

  • Installations and Configurations
  • Java
  • ORM
  • Spring Boot
  • Spring Boot HikariCP Connection Pooling

Archives

  • December 2021
  • August 2021
  • November 2020
  • March 2020
  • August 2018
  • November 2016
  • August 2016

Recent Posts

  • Another Log4j Bug – DoS
  • Log4j Vulnerability / Version Upgrade to 2.16.0 by Apache Team
  • Fixing Log4j Vulnerability
  • Log4J (RCE) Vulnerability
  • JPA vs Hibernate – Specification Vs Implementation

Categories

  • Installations and Configurations
  • Java
  • ORM
  • Spring Boot
  • Spring Boot HikariCP Connection Pooling

Archives

  • December 2021
  • August 2021
  • November 2020
  • March 2020
  • August 2018
  • November 2016
  • August 2016




Recent Posts

  • Another Log4j Bug – DoS
  • Log4j Vulnerability / Version Upgrade to 2.16.0 by Apache Team
  • Fixing Log4j Vulnerability
  • Log4J (RCE) Vulnerability
  • JPA vs Hibernate – Specification Vs Implementation

Categories

  • Installations and Configurations
  • Java
  • ORM
  • Spring Boot
  • Spring Boot HikariCP Connection Pooling
  • HikariCP Connection Pooling for Spring Boot for 1.x version Spring Boot
  • Sonar Qube – Code Coverage and Code Quality Tool Installations and Configurations
  • JPA vs Hibernate – Specification Vs Implementation ORM
  • HikariCP Configurations – Database Connection Pooling Installations and Configurations
  • Unique Random ‘N’ digit Number generator Java
  • Why to have a private constructor? Java
  • Log4j Vulnerability / Version Upgrade to 2.16.0 by Apache Team Java
  • Another Log4j Bug – DoS Java

Copyright © 2023 Santhosh Ponnam.

Powered by PressBook News WordPress theme