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

Missing database name in error message from LogToFile.stopReplicationSlaveRole()

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.11.1.1
    • Fix Version/s: None
    • Component/s: Store
    • Labels:
      None

      Description

      I saw this error in derby.log after running replication tests:

      ERROR 08006: Database '{0}' shutdown.
      	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:290)
      	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:285)
      	at org.apache.derby.impl.store.raw.log.LogToFile.stopReplicationSlaveRole(LogToFile.java:5253)
      	at org.apache.derby.impl.store.replication.slave.SlaveController.stopSlave(SlaveController.java:266)
      	at org.apache.derby.impl.store.replication.slave.SlaveController.access$500(SlaveController.java:64)
      	at org.apache.derby.impl.store.replication.slave.SlaveController$SlaveLogReceiverThread.run(SlaveController.java:526)
      

      The database name is missing from the message.

      LogToFile.stopReplicationSlaveRole() should either call newException() with the database name as argument or use another message that doesn't take a database name argument.

        Attachments

          Activity

            People

            • Assignee:
              rajitharajasooriya Rajitha rajasooriya
              Reporter:
              knutanders Knut Anders Hatlen
            • Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: