TOMCAT could not be started due to a port conflict

Document ID : KB000026261
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem: 

When the command "caf start tomcat" is executed, Tomcat is started and stopped immediately.

 

Environment:  

CA Client Automation - All Versions

 

Cause:

The Command "caf start tomcat" starts a java.exe process. This process tries to bind to 3 TCP ports :

8020 (AJP)
8095 (shutdown)
8090 (startup)

Sometimes some of these ports are already used by another application which may prevent DSM tomcat from starting.
Use a tool like TCPView (http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx) in order to find out which process' are using these ports.

 

Resolution:

 A solution to change the TCP port used by DSM TOMCAT:

  1. Edit the file C:\program files\CA\DSM\Web Console\conf\server.xml using Wordpad.

  2. Change the port numbers with unused port numbers.
    Ex:
    Change port="8095" with port="8096"
    Change port="8090" with port="8091"
    Change port="8020" with port="8021"

  3. Start tomcat using:
    caf start tomcat