How to Solve CQ Port Conflicts on Windows

If you get the following error message on the CQ startup, you have a port conflict problem. Some other service on the same server instance is using the same TCP LISTEN port that CQ is configured to listen on.

PortSelector: Selecting server port from supplied list: 4502
PortSelector: Trying port 4502
PortSelector: java.net.BindException: Address already in use: JVM_Bind
java.io.IOException: Did not find an available server port, tried 4502
at com.day.crx.quickstart.PortSelector.selectPort(PortSelector.java:66) at com.day.crx.quickstart.Quickstart.<init>(Quickstart.java:197)
at com.day.crx.quickstart.Main.<init>(Main.java:667)
at com.day.crx.quickstart.Main.main(Main.java:730)
Quickstart: aborting
MAIN process: shutdown hook
MAIN process: exiting 

Use Microsoft’s TCPView tool to determine which process is using the port. If it cannot be shut down, you’ll have to have CQ run with a different TCP LISTEN port. To do this, you can rename your CQ JAR file to include -port. For example, to have an “author” instance of CQ listen on port 4510, name the JAR file CQ5.4-author-4510.jar