search

zkfan / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

trepctl should take the RMI port from configuration files #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
when running the replicator with a non-standard RMI port,
trepctl does not use the port indicated in the configuration files, but it uses 
its defaults.
Instead, it should use the port mentioned in static.servicename.properties, 
unless users say otherwise with the --port option

Original issue reported on code.google.com by g.maxia on 23 May 2011 at 1:07

GoogleCodeExporter commented 9 years ago 
This appears to be an example of a variable that should properly be set in the 
services.properties file as it is global across the replicator and all 
replication services.  The value should be read and set at replicator process 
start-up.  All other values and/or logic to manipulate the RMI port should be 
eliminated.

Original comment by berkeley...@gmail.com on 23 May 2011 at 8:44

GoogleCodeExporter commented 9 years ago 
ReplicationServiceManager, as it stands currently, is reading rmi_port and 
rmi_host properties from the instance-global services.properties file, as 
expected. On the other hand, rmi_port parameter in static-<service>.properties 
is not read and is introducing confusion.

Original comment by linas.vi...@gmail.com on 24 May 2011 at 7:53

GoogleCodeExporter commented 9 years ago 
It would be desirable to remove the rmi_port from the 
static-<service>.properties files, leaving it only as a comment 
(e.g: # RMI port set as 10040 at 12:34:56 2001-05-23)

Original comment by g.maxia on 24 May 2011 at 8:06

GoogleCodeExporter commented 9 years ago

Original comment by jeffm...@gmail.com on 19 Jun 2011 at 6:44