db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3428) Doing a replication failover should shutdown the database and the connection should no longer be available
Date Mon, 18 Feb 2008 06:42:34 GMT
Doing a replication failover should shutdown the database and the connection should no longer
be available
----------------------------------------------------------------------------------------------------------

                 Key: DERBY-3428
                 URL: https://issues.apache.org/jira/browse/DERBY-3428
             Project: Derby
          Issue Type: Bug
            Reporter: V.Narayanan


Oystein says (as part of comments in Derby-3205)

After executing a failover, I am told that the database is shut down, but I still able to
use the connection to access the database:

ij version 10.4
ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
ij> call syscs_util.syscs_freeze_database();
0 rows inserted/updated/deleted
ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost';
ij(CONNECTION1)> call syscs_util.syscs_unfreeze_database();
0 rows inserted/updated/deleted
ij(CONNECTION1)> connect 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true';
ERROR XRE20: Failover performed successfully for database 'null', the database has been shutdown.
ij(CONNECTION1)> select * from t;
I
-----------
1
2
3
4
5
6
7
8
9
10
10

11 rows selected
ij(CONNECTION1)>

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