db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Closed: (DERBY-3394) 'NetworkServerControl shutdown' does not complete on master server after 'failover'.
Date Tue, 04 Mar 2008 08:51:52 GMT

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

Jørgen Løland closed DERBY-3394.
--------------------------------


> 'NetworkServerControl shutdown' does not complete on master server after 'failover'.
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-3394
>                 URL: https://issues.apache.org/jira/browse/DERBY-3394
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>         Environment: svn r618655 + derby-3361-1b.diff
>            Reporter: Ole Solberg
>
> Master and slave servers startet.
> Copy db from master to slave:
> Master:
> CONNECT 'jdbc:derby://urd11:8888/test';
> call syscs_util.syscs_freeze_database();
> In slave db directory:
> scp -r urd11:/export/home/tmp/os136789/Replication_common_Trunk/master/test ./
> Master:
> CONNECT 'jdbc:derby://urd11:8888/test';
> call syscs_util.syscs_unfreeze_database(); -- Should be done by startMaster....
> Slave:
> 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. 
> Master:
> CONNECT 'jdbc:derby://urd11:8888/test;startMaster=true;slaveHost=urd12;slavePort=8989';
> (OK.)
> Run "insert and select test" on master db. OK.
> Master:
> CONNECT 'jdbc:derby://urd11:8888/test;failover=true';
> ERROR XRE20: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE20, SQLERRMC: Failover performed
successfully for database 'test', the database has been shutdown.
> (OK.)
> Slave derby.log:
> Failover perfomed successfully for database 'test'.
> Master derby.log:
> 2008-02-06 12:17:10.602 GMT Thread[DRDAConnThread_2,5,main] (DATABASE = test), (DRDAID
= {5}), Failover performed successfully for database 'test', the database has been shutdown.
> Connections to master db are ok:
> [os136789@supra05:common_Trunk] java org.apache.derby.tools.ij
> ij version 10.4
> ij> DRIVER 'org.apache.derby.jdbc.ClientDriver';
> ij> CONNECT 'jdbc:derby://urd11:8888/test';
> ij> select * from t;
> K          |S                                                                       
                                                       
> --------------------------------------------------------------------------------------------------------------------------------------------
> 1          |1111111                                                                 
                                                       
> .
> 600        |600                                                                     
                                                       
> 21 rows selected
> Master derby.log: no change....
> On master host: attempted shutdown is not completed. <=====================================
> .NetworkServerControl shutdown
> Apache Derby Network Server - 10.4.0.0 alpha - (618655M) shutdown at 2008-02-06 12:19:21.586
GMT
> But the server is still running:
> [os136789@urd11:master] ps auxwww | grep drda
> os136789 12797  0.4  2.7 192872 28652 pts/0  Sl   13:12   0:02 java -cp /home/os136789/Replication/common_Trunk/trunk/jars/insane/derbynet.jar
org.apache.derby.drda.NetworkServerControl start -h 0.0.0.0 -p 8888 -noSecurityManager
> Master derby.log: no change....
> Connections to the db now are refused:
> CONNECT 'jdbc:derby://urd11:8888/test';
> ERROR 08001: java.net.ConnectException : Error connecting to server urd11 on port 8888
with message Connection refused.

-- 
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