db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-3374) Hang in master server if startMaster command is given twice
Date Fri, 04 Apr 2008 14:31:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ole Solberg closed DERBY-3374.
------------------------------


> Hang in master server if startMaster command is given twice
> -----------------------------------------------------------
>
>                 Key: DERBY-3374
>                 URL: https://issues.apache.org/jira/browse/DERBY-3374
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>         Environment: Trunk (615841) + patch DERBY-3205/stopSlave_v1b
>            Reporter: Ole Solberg
>            Assignee: V.Narayanan
>             Fix For: 10.4.0.0
>
>
> master and slave servers started.
> startSlave:
> ij> CONNECT 'jdbc:derby://urd12:9999/test;startSlave=true;slaveHost=urd12;slavePort=8989';
>         ERROR XRE08: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE08, SQLERRMC: Replication
slave mode started successfully for database 'test'. Connection refused because the database
is in replication slave mode. 
> slave derby.log:
> Replication slave role started for database 'test'.
> startMaster:
> ij> CONNECT 'jdbc:derby://urd11:8888/test;startMaster=true;slaveHost=urd12;slavePort=8989';
> ij> 
> master derby.log:
> Replication master role started for database 'null'.
> 2. startMaster:
> ij> CONNECT 'jdbc:derby://urd11:8888/test;startMaster=true;slaveHost=urd12;slavePort=8989';
> ij does not return.
> No output to master OR slave derby.log.

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


Mime
View raw message