Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1539594005.1204631920770.JavaMail.jira@brutus>
Date: Tue, 4 Mar 2008 03:58:40 -0800 (PST)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3447) Shutdown on a database without
 stopping replication hangs
In-Reply-To: <1739394229.1203672979741.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-3447?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1257=
4946#action_12574946 ]=20

J=C3=B8rgen L=C3=B8land commented on DERBY-3447:
--------------------------------------

When replication has been set up in embedded using ij,

connect 'jdbc:derby:;shutdown=3Dtrue'
quit;

works fine on the master, whereas only

quit;

hangs. I'm not sure what the difference here is, but the thread stack repor=
ts that the log shipper thread is still alive. I think we shoul add cleanup=
 code in MC#stop to get rid of this thread in the case that the module is u=
nbooted without calling stopMaster or failover first. That happens e.g. for=
 system shutdown.

> 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
>


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