[
https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579387#action_12579387
]
V.Narayanan commented on DERBY-3447:
------------------------------------
Sorry the comment I deleted was a click too quick.
The part of the replication test where the failure occurs tries to test a slave
shutdown after the master has been taken down.
I tried doing the above manually and observe the following
ij> connect
'jdbc:derby://localhost:1528/replicationdb;user=oystein;password=pass;stopSlave=true';
ERROR XRE41: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE41, SQLERRMC: XRE41
ij> connect
'jdbc:derby://localhost:1528/replicationdb;user=oystein;password=pass;stopSlave=true';
ERROR XRE42: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE42, SQLERRMC:
replicationdbXRE42
ij>
So before the master is killed the slave take down attempt fails XRE41
and after the master is killed it succeeds XRE42.
Seems like the code is behaving as the tests ask it too. I will investigate
further into this.
> Shutdown on a database without stopping replication hangs
> ---------------------------------------------------------
>
> Key: DERBY-3447
> URL: https://issues.apache.org/jira/browse/DERBY-3447
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: Derby3447_v1.diff, Derby3447_v1.stat, Derby3447_v2.diff,
> Derby3447_v2.stat, Derby3447_v3.diff, Derby3447_v3.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
