[
https://issues.apache.org/jira/browse/DERBY-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575654#action_12575654
]
Knut Anders Hatlen commented on DERBY-3388:
-------------------------------------------
By the way, I think my question (6) was a bit inaccurate. It seems like the
intervals and the buffer size can be persisted in derby.properties (since
PropertyUtil.getSystemProperty() doesn't only look at system properties, as I
though it did). But still, it would make sense to have those properties
configurable with database granularity instead of system granularity, wouldn't
it?
> 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.0.0
> Reporter: Jørgen Løland
> Assignee: Jørgen Løland
> Priority: Minor
> 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
>
>
> 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.
