[
https://issues.apache.org/jira/browse/DERBY-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099546#comment-16099546
]
Rajitha rajasooriya commented on DERBY-6711:
--------------------------------------------
Can you please provide the steps of what you've done ??
> Missing database name in error message from
> LogToFile.stopReplicationSlaveRole()
> --------------------------------------------------------------------------------
>
> Key: DERBY-6711
> URL: https://issues.apache.org/jira/browse/DERBY-6711
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.11.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Rajitha rajasooriya
> Priority: Minor
>
> I saw this error in derby.log after running replication tests:
> {noformat}
> 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)
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
