Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3417

slave side stop in a client server mode results in SQLState printed without proper error message

    Details

    • 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
    • Labels:
      None

      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.

        Attachments

        1. derby-3417-2.stat
          0.8 kB
          Dag H. Wanvik
        2. derby-3417-2.diff
          22 kB
          Dag H. Wanvik
        3. derby-3417.stat
          0.7 kB
          Dag H. Wanvik
        4. derby-3417.diff
          19 kB
          Dag H. Wanvik

          Activity

            People

            • Assignee:
              dagw Dag H. Wanvik
              Reporter:
              narayanan V.Narayanan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: