View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003706||SymmetricDS||Bug||public||2018-09-05 13:12||2018-10-31 14:19|
|Target Version||3.9.16||Fixed in Version|
|Summary||0003706: Marking Log file type monitor events as resolved causes a new log file event to appear|
|Description||If 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.