[
https://issues.apache.org/jira/browse/DERBY-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øystein Grøvlen updated DERBY-3437:
-----------------------------------
Derby Info: (was: [Patch Available])
Thanks for this useful patch, Serge. I have already had use of it when
debugging 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ørgen Løland
> Assignee: Serge Tsv
> Priority: Minor
> Attachments: DERBY-3437-1.diff, DERBY-3437-1.stat, 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.
