You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jørgen Løland (JIRA)" <ji...@apache.org> on 2009/11/26 07:13:39 UTC
[jira] Resolved: (DERBY-3388) Improve message handling for
replication messages to derby.log
[ https://issues.apache.org/jira/browse/DERBY-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland resolved DERBY-3388.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.4.1.3
> Improve message handling for replication messages to derby.log
> --------------------------------------------------------------
>
> Key: DERBY-3388
> URL: https://issues.apache.org/jira/browse/DERBY-3388
> Project: Derby
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 10.4.1.3
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
> Priority: Minor
> Fix For: 10.4.1.3
>
> Attachments: derby-3388-tstamp-and-properties-1a.diff, derby-3388-tstamp-and-properties-1a.stat, derby-3388-tstamp-and-properties-1b.diff, derby-3388-tstamp-and-properties-1b.stat, derby-3388-tstamp-and-properties-1c.diff, derby-3388-tstamp-and-properties-1c.stat
>
>
> The asynchronous replication functionality writes information to the derby log. It would be good to improve this in the following ways:
> 1: startSlave and stopSlave stack traces are written twice to the log - one is obviously enough :)
> 2: It should be possible to configure if replication messages written to the log should be followed by a stack trace of the cause.
> 3: logged messages should have a timestamp
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.