Orchestrator service stops immediately after start
search cancel

Orchestrator service stops immediately after start

book

Article ID: 46308

calendar_today

Updated On:

Products

CA Process Automation Base

Issue/Introduction

After installing Process Automation we see service stops automatically after start and c2o.log shows following errors.

 

ERROR [com.optinuity.c2o.transport.TransportServer] [ Initialization] Exception starting server 

java.net.BindException: Address already in use: bind 

at sun.nio.ch.Net.bind0(Native Method) 

at com.optinuity.c2o.c2oserver.ServerManager.initializeFullServer(ServerManager.java:547) 

at com.ca.pam.frontcontroller.ConfiguratorServlet$1.run(ConfiguratorServlet.java:41) 

ERROR [com.optinuity.c2o.c2oserver.ServerManager] [ Initialization] Exception occurred while booting up the Server 

 

Environment

Process Automation - All supported versions

Cause

This error is seen when web server port specified during installation is used by another application.

The default port used by web server is 80 which is also the default port used by IIS.

Resolution

1. Stop the other application that is using the port then start Process Automation service

Or

2. Reconfigure Process Automation to use another port for web server