Actions
Bug #3885
closedKNB metacat replication error log file is empty
Start date:
03/12/2009
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
3885
Description
In the new 1.9.0 knb metacat, it seems the replication log files' name are changed. Somehow the error log file is empty - but it shouldn't since we know some eml documents were not replicated successfully.
Duane sent us an email with a replication error log file. That file is not empty and this means that the replication error log works on lter metacat.
Updated by Michael Daigle about 15 years ago
There are several errors in ReplicationHandler that only report to the metacat log. These should report to the replication log as well.
Updated by Michael Daigle over 14 years ago
Changed replication logging to use log4j rollingfileappender. Changed all replication logging to use this appender.
Actions