[
https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579386#action_12579386
]
V.Narayanan commented on DERBY-3447:
------------------------------------
The place in the replication test where this failure occurs
org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1_1._testPostStartedMasterAndSlave_StopSlave(ReplicationRun_Local_StateTest_part1_1.java:222)
at
seems to be testing
assertTrue(connectionURL + " failed: " + msg,
SQLState.REPLICATION_SLAVE_SHUTDOWN_OK.equals(ss));
whether the slave has been shutdown successfully
after calling a stopSlave on the slave
// 3. stopSlave on slave should now be allowed. Observe that the database
shall be shutdown.
db = slaveDatabasePath +FS+ReplicationRun.slaveDbSubPath +FS+
replicatedDb;
connectionURL = "jdbc:derby:"
+ "//" + slaveServerHost + ":" + slaveServerPort + "/"
+ db
+ ";stopSlave=true";
boolean stopSlaveCorrect = false;
util.DEBUG("3. testPostStartedMasterAndSlave_StopSlave: " +
connectionURL);
try
{
conn = DriverManager.getConnection(connectionURL); // From anywhere
against slaveServerHost?
util.DEBUG("Unexpectedly connected: " + connectionURL);
assertTrue("Unexpectedly connected: " + connectionURL,false);
}
stopSlave on the slave should result in an exception after a successful
connection with the master shouldn't it?
In that context I am not sure about this comment on the above code also
// 3. stopSlave on slave should now be allowed. Observe that the database
shall be shutdown.
> 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.
