It's possible to run multiple CostOS Server instances on one machine as long as the instance completes the following requirements:

  • Not sharing the same listening port of any other instance or service.
  • Not sharing the same database with another instance.
  • When using services within windows, using 2 different windows service definitions.
  • Not sharing the same CostOS Server home folder.
  • Having separate licenses for each of the instances.

By default, CostOS Server runs on port 8080 and JMS port 61616 (and hence is available at (http://<yourserver>:8080/ces, eg. http://localhost:8080/ces).

If you want to run another CostOS Server instance but already has a service claiming port 8080 and 61616, there will be a conflict, and CostOS Server will fail to start. You may see errors like this:

Protocol handler initialization failed: java.net.BindException: Address already in use:8080

This can be fixed by changing CostOS Server to use another listening port (eg. 8081) and JMS port (eg. 61617). This is done during the installation on configuration window:

Here, change the JMS port from "61616" to "61617" and change the listening port from "8080" to "8081" (or some other free port). 

Which port number should I choose? 

If you are not sure which port number to choose, use a tool such as netstat to determine which port numbers are free to use by  CostOS Server. The highest port number that can be used is 65535 because it is the highest number which can be represented by an unsigned 16 bit binary number. 

If you want to run another CostOS Server instance but already has a Windows service. This can be fixed by creating an additional CostOS Server Windows service. This is done during the installation on configuration window:

Update/Configure Multiple Instances

To update an instance of CostOS server between several installed instances.

1.Run Installation Media

2.Define the installation that you want to update clicking 'Perform Mandatory update Action'