[
https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3447:
-------------------------------
Attachment: Derby3447_v3.stat
Derby3447_v3.diff
I believe it is not right for the replication threads to prevent the jvm running
an embedded application (like ij) from shutting down. These threads should also
be brought down along with the jvm. Hence I believe that the replication
threads should be daemon threads so that when the vm exits these threads
are also brought down along with the vm.
Converting the following replication related threads to
Daemon threads resolved the problem of these threads blocking
the ij process from executing a quit; on both the master and
the slave.
1) Slave database boot thread (slave)
2) Log receiver thread (slave)
3) Log shipper thread (master)
I will run the replication suite of tests and shall revert back with
results for this patch.
I request for this patch to be please considered for reviews/comments.
> 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
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
