[
https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584425#action_12584425
]
V.Narayanan commented on DERBY-3552:
------------------------------------
>I guess the jar installation is recorded in the transaction log that gets sent
>over to the slave an applied, so the slave thinks the jars are there even
>though
>they aren't?
correct
>It seems as if the error message when you try to run startSlave is rather
>misleading.
>It says the database is in slave mode, even after a failover, when it is not
>actually in
>slave mode and the real problem is the jar problem. I may be misunderstanding
>the context,
>though.
When this message is thrown
ERROR 08004: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC:
Connection refused to database 'replicationdb' because it is in replication
slave mode.
We have not attempted failover yet. I just posted that message for completeness
sake.
Failover is attempted before taking a connection to the slave database (i.e.)
before this step
ij> connect 'jdbc:derby://localhost:1528/replicationdb';
It succeeds without throwing any exception
> Handle jar files that are installed when replication is enabled
> ---------------------------------------------------------------
>
> Key: DERBY-3552
> URL: https://issues.apache.org/jira/browse/DERBY-3552
> Project: Derby
> Issue Type: Sub-task
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
