[
https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574600#action_12574600
]
Serge Tsv commented on DERBY-3489:
----------------------------------
Some additional thoughts about the 2nd issue.
There's a public SlaveAddress class which "Encapsulates the host name and the
port number
of the slave machine. I think is might be considered to create an instance of
SlaveAddress
and use this instance inside both SlaveController and MasterController, instead
of having
two separate hostname/port variables. Then all the default port related logic
will be
encapsulated only in a single class, and not scattered among different
replication classes.
> Error message XRE04 does not include the right port number.
> -----------------------------------------------------------
>
> Key: DERBY-3489
> URL: https://issues.apache.org/jira/browse/DERBY-3489
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: Øystein Grøvlen
>
> If the master is not able to connect to the slave, the error messages does
> not include the right port number:
> ij> connect
> 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost;slavePort=9901';
> ERROR XRE04: Could not establish a connection to the peer of the replicated
> database 'masterDB' on address 'localhost:-1'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
