AXA - install fails because of port conflict

Document ID : KB000095547
Last Modified Date : 05/07/2018
Show Technical Document Details
Issue:
AXA 17.3 installation aborted because cannot start Jarvis on port 8081 because of a bind faiilure.  Jarvis Schema Registry utilizes port 8081 which is commonly utilized in third party software.   This will cause a bind failure of this component and fail the AXA install. 
Resolution:
The only current workaround is to free 8081 for the installation.  Once the installation is completed, then you can perform the following steps and re-enable the third party software.
  • Edit $CA_EMM_HOME/jarvis/schema_registry/config/schema-registry.properties
  • In ‘listeners’ property, change a value from http://<Host>:8081 to http://<Host>:8085 or any other open port
Other Jarvis processes that rely on the schema registry will need their configuration changed to point to the new port
  • In the following files
$CA_EMM_HOME//jarvis/config/apis.properties
$CA_EMM_HOME//jarvis/config/verifier.properties
$CA_EMM_HOME//jarvis/config/indexer.properties
$CA_EMM_HOME//jarvis/config/utils.properties
 
 
update the port setting of this property in each file:
 
schema_registries = http://<host>:8081
  • Restart all services.