db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-3388) Improve message handling for replication messages to derby.log
Date Tue, 05 Feb 2008 10:40:08 GMT
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
            Priority: Minor


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.


Mime
View raw message