[DERBY-3417] slave side stop in a client server mode results in SQLState printed without proper error message

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.5.2.0, 10.6.1.0
• Component/s: Replication
• Assignee: Dag H. Wanvik
• Reporter: V.Narayanan
• Created: 14/Feb/08 10:18
• Updated: 16/Jul/09 21:24
• Resolved: 29/Apr/09 00:16

Description

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.