[
https://issues.apache.org/jira/browse/DERBY-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516291
]
V.Narayanan commented on DERBY-2921:
------------------------------------
ome Questions for which I do not have an answer in this implementation
1) Replication would by default use the port number 8001 if the user
does not specify the port number. The number 8001 was chosen
randomly. Is it OK to do it this way? If no how should the
port be chosen?
2) When a error occurs in the Transmitter or the Receiver it is
bundled in a StandardException and thrown with a SQLState of
XR001, XR002 etc.
The logic behind choosing this was
X - Means derby specific. I understood this from a scan of
SQLState.java
R - Replication specific.
The last three digits would be sequential.
Is this the correct way of assigning the SQLState?
Is it OK to bundle the exceptions in a StandardException and
throw them.
3) In the receiver the accept() method on the socket is called
from the run method.
We cannot throw checked exceptions from a run method. This has been
handled this by bundling the exception thrown in a RuntimeException
and throwing it.
The way it is done in impl/drda/ClientThread.java does not offer a
clue as to how this is to be done as there we print console messages
which would not be possible in this case.
Is RuntimeException the way out here? Is there a better way of doing
this?
> Replication: Add a network service that connects the master and slave Derby
> instances
> -------------------------------------------------------------------------------------
>
> Key: DERBY-2921
> URL: https://issues.apache.org/jira/browse/DERBY-2921
> Project: Derby
> Issue Type: Sub-task
> Components: Services
> Affects Versions: 10.4.0.0
> Reporter: Jørgen Løland
> Assignee: V.Narayanan
> Attachments: Replication_Network_v1.diff, Replication_Network_v1.stat
>
>
> A network connection is required between the master and slave Derby instances
> of a replicated database. The connection will be used to send many kinds of
> messages, including:
> * log records
> * the database (when replication is started)
> * master -> slave commands (like "stop replication")
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
