Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1984257478.1204634200978.JavaMail.jira@brutus>
Date: Tue, 4 Mar 2008 04:36:40 -0800 (PST)
From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3437) Give all replication threads
 meaningfull names
In-Reply-To: <1514444741.1203513583670.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-3437?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

=C3=98ystein Gr=C3=B8vlen updated DERBY-3437:
-----------------------------------

    Derby Info:   (was: [Patch Available])

Thanks for this useful patch, Serge.  I have already had use of it when deb=
ugging replication.
Committed as revision 633451.

> Give all replication threads meaningfull names
> ----------------------------------------------
>
>                 Key: DERBY-3437
>                 URL: https://issues.apache.org/jira/browse/DERBY-3437
>             Project: Derby
>          Issue Type: Improvement
>          Components: Newcomer, Replication
>    Affects Versions: 10.4.0.0
>            Reporter: J=C3=B8rgen L=C3=B8land
>            Assignee: Serge Tsv
>            Priority: Minor
>         Attachments: DERBY-3437-1.diff, DERBY-3437-1.stat, DERBY-3437.dif=
f
>
>
> Some threads are created for replication purposes:
> * The log shipper thread on the master (o.a.d.i.services.master.MasterCon=
troller)
> * The database boot thread on the slave (o.a.d.i.db.SlaveDatabase)
> * The log receiver thread on the slave (o.a.d.i.services.slave.SlaveContr=
oller)
> These threads should be given names to simplify debugging.

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