[ 
https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576548#action_12576548
 ] 

V.Narayanan commented on DERBY-3162:
------------------------------------

>I am seeing messages like 'Warning: UnknkownHostException: OLESO-FERRARI: 
>OLESO-FERRARI.'
>in connection with InetAddress.getByName(hostName) in 
>ReplicationRun.pingServer.

I checked the ping code, seems harmless and also seems to conform to what 
NetworkServerControl
comments asks you to do

ping code -

ping( new NetworkServerControl(InetAddress.getByName(hostName),port), 
iterations);

NetworkServerControl comments -

This is an example of starting and shutting down the Network Server in the 
example
above with the API.

NetworkServerControl serverControl = new 
NetworkServerControl(InetAddress.getByName("myhost"),1621)
serverControl.shutdown();

Looks like a lookup failure in windows to me,

I am not sure that your code is at fault.

> Create a framework for replication tests
> ----------------------------------------
>
>                 Key: DERBY-3162
>                 URL: https://issues.apache.org/jira/browse/DERBY-3162
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.4.0.0
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: derby-3162.1-v1.diff.txt, derby-3162.2-v2.diff.txt, 
> derby-3162.2-v2.stat.txt, derby-3162.3-v1.diff.txt, derby-3162.3-v1.stat.txt, 
> derby-3162.3-v2.diff.txt, derby-3162.3-v2.stat.txt, derby-3162.3-v3.diff.txt, 
> derby-3162.3-v3.stat.txt, derby-3162.3-v4c.diff.txt, 
> derby-3162.3-v4c.stat.txt, derby-3162.3-v4d.diff.txt, 
> derby-3162.3-v4d.stat.txt, derby-3162.4-v1.diff.txt, 
> derby-3162.4-v1.stat.txt, derby-3162.4-v2.diff.txt, derby-3162.4-v2.stat.txt
>
>
> Handle
>  - starting and stopping Derby servers to have the master and slave 
> replication roles,
>  - doing administrative commands like startreplication, startslave, 
> stopreplication, failover,
>  - performing consistency checks on the slave vs. the master,
>  - running load clients against master and slave in the various states of 
> replication,
>  - provoking error situations on master and slave, and network,
>  - ... 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to