db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3235) Implement the replication stop functionality
Date Mon, 21 Jan 2008 13:01:39 GMT

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

Øystein Grøvlen commented on DERBY-3235:
----------------------------------------

Patch, StopImplementation_v3.diff, committed as revision 613866.
I tested that it is now possible to quit ij after the master has been stopped.

However, if I shut down the database without stopping replication, I still get the hang.
I think we need to stop the LogShipperThread in that case, too.  (Alternatively, we could
prevent
shut down of replicated databases). 


> 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: 10.4.0.0
>            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.


Mime
View raw message