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-3437) Give all replication threads meaningfull names
Date Tue, 26 Feb 2008 13:09:51 GMT

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

Øystein Grøvlen commented on DERBY-3437:

Serge, thanks for the patch.  It looks good.  Would it be possible to create it relative to
the trunk directory.   That would make it easier for me to apply it.

For the log shipper issue, either of your first two suggestions is OK with me.  I do not think
it is a good idea to move the class since there is a possibility that we will have several
implementations of the LogShipper interface in the future.

> 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:
>            Reporter: Jørgen Løland
>            Assignee: Serge Tsv
>            Priority: Minor
>         Attachments: DERBY-3437.diff
> Some threads are created for replication purposes:
> * The log shipper thread on the master (o.a.d.i.services.master.MasterController)
> * 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.SlaveController)
> These threads should be given names to simplify debugging.

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

View raw message