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-3417) slave side stop in a client server mode results in SQLState printed without proper error message
Date Thu, 14 Feb 2008 10:19:09 GMT
slave side stop in a client server mode results in SQLState printed without proper error message
------------------------------------------------------------------------------------------------

                 Key: DERBY-3417
                 URL: https://issues.apache.org/jira/browse/DERBY-3417
             Project: Derby
          Issue Type: Bug
          Components: Replication
    Affects Versions: 10.4.0.0
            Reporter: V.Narayanan
             Fix For: 10.4.0.0


I tried a stopSlave on the slave side of the replication system and
found the below

ij> connect 'jdbc:derby://localhost:1528/replicationdb;stopSlave=true';
ERROR XRE41: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE41, SQLERRMC: XRE41

https://issues.apache.org/jira/browse/DERBY-3205 says

ERROR XRE41: Replication operation 'failover' or 'stopSlave' failed because the connection
with the master is working. Issue the 'failover' or 'stopMaster' operation on the master database
instead.

needs  to be printed.

I am not sure if this is a generic case for client server replication messages.

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