db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3235) Implement the replication stop functionality
Date Mon, 21 Jan 2008 13:18:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561003#action_12561003

Jørgen Løland commented on DERBY-3235:

> Alternatively, we could prevent shut down of replicated databases

I don't think that's an option since that would break the shutdown server functionality. From
the top of my head, I think server shutdown is implemented by first shutting down all booted
databases and then shut down the server. If you throw an exception, e.g., shutdown server
would result in a shutdown of the databases that by chance were iterated over before the replicated
database was attempted shut down, but not the rest. Unless, of course, you want to change
the shutdown server functionality as well...

> Implement the replication stop functionality
> --------------------------------------------
>                 Key: DERBY-3235
>                 URL: https://issues.apache.org/jira/browse/DERBY-3235
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Replication
>    Affects Versions:
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: StopImplementation_v1.diff, StopImplementation_v1.stat, StopImplementation_v1_NotForCommit.diff,
StopImplementation_v1_NotForCommit.stat, StopImplementation_v2.diff, StopImplementation_v2.stat,
StopImplementation_v3.diff, StopImplementation_v3.stat

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message