View Issue Details

IDProjectCategoryView StatusLast Update
0003706SymmetricDSBugpublic2018-10-31 14:19
ReporterhanesAssigned Tojosh-a-hicks 
Priorityhigh 
Status assignedResolutionopen 
Product Version3.9.12 
Target Version3.9.16Fixed in Version 
Summary0003706: Marking Log file type monitor events as resolved causes a new log file event to appear
DescriptionIf you create a situation where a stack trace appears in the log, a monitor event is recorded. SymmetricDS is smart enough not to create multiple copies of that monitor event. BUT, if you mark that event as "resolved", it turns around and creates another copy of that event. Perhaps whatever it's using to determine if there's already an event representing the monitor that fires is (incorrectly) filtering out already-resolved events? Also, I'm not sure, but I think restarting the node fixes the issue, as does clearing the log.

More generally speaking, I've also had trouble consistently causing the monitor event to fire. I've had times where I've cause a stack trace to appear in the log yet the monitor doesn't fire, despite waiting more than enough time.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2018-09-05 13:12 hanes New Issue
2018-09-05 13:12 hanes Status new => assigned
2018-09-05 13:12 hanes Assigned To => josh-a-hicks
2018-10-03 13:37 hanes Target Version => 3.9.15
2018-10-31 14:19 admin Target Version 3.9.15 => 3.9.16