[
https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3447:
-------------------------------
Attachment: Derby3447_v5.stat
Derby3447_v5.diff
Thank you for taking a look at the patch Oystein
I intended the message to be printed that way (similar to the printStackTrace
and stop method)
I have two justifications for this
1) The only time the message is thrown is when the master has already stopped
2) It is like saying the master has stopped but the following exception
occurred (which is this case is only when the master is stopped)
I have fixed the nits pointed out.
I was hoping to submit regression tests in a follow up.
> Shutdown on a database without stopping replication hangs
> ---------------------------------------------------------
>
> Key: DERBY-3447
> URL: https://issues.apache.org/jira/browse/DERBY-3447
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: Derby3447_v1.diff, Derby3447_v1.stat, Derby3447_v2.diff,
> Derby3447_v2.stat, Derby3447_v3.diff, Derby3447_v3.stat, Derby3447_v4.diff,
> Derby3447_v4.stat, Derby3447_v5.diff, Derby3447_v5.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
