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] Commented: (DERBY-3428) Doing a replication failover should shutdown the database and the connection should no longer be available
Date Tue, 26 Feb 2008 19:44:51 GMT

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

Jørgen Løland commented on DERBY-3428:
--------------------------------------

Hi Narayanan,

I tried the latest patch. In embedded, the patch works as expected:

ij> connect 'jdbc:derby:test;startMaster=true;slaveHost=localhost';
ij(CONNECTION1)> connect 'jdbc:derby:test;failover=true';
ERROR XRE20: Failover performed successfully for database 'test', the database has been shutdown.
ij(CONNECTION1)> show tables;
ERROR 08003: No current connection.


but in client/server I get:

ij> connect 'jdbc:derby://localhost:1527/test;startMaster=true;slaveHost=localhost';
ij(CONNECTION1)> connect 'jdbc:derby://localhost:1527/test;failover=true';
ERROR XRE20: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE20, SQLERRMC: Failover performed successfully
for database 'test', the database has been shutdown.
ij(CONNECTION1)> show tables;
ERROR 08006: A network protocol error was encountered and the connection has been terminated:
the requested command encountered an unarchitected and implementation-specific condition for
which there was no architected message

Derby.log does not contain more info than the failover successful stack trace.

Do we need a new jira for this?

> 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
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: Derby3428.diff, Derby3428.stat, Derby3428_v1.diff, Derby3428_v1.stat
>
>
> 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