Bug #9417
Errors might not be logged by the LegacyLogManager.
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
trunk/15595
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Artur Școlnic over 1 year ago
LOG-MANAGER:LOGFILE-NAME = "file.log".
do on error undo:
undo, throw new Progress.Lang.AppError("Error", 1).
end.
This example shows that not all errors are logged by the LegacyLogManager, mainly the logging is enabled in the
ErrorManager, but there are methods that throw errors and do not log them, undoThrow is an example.This issue originated from #9271-24.
undoThrow will be solved by 9271a, but there might be other cases.#3 Updated by Greg Shah over 1 year ago
+Galya, +Constantin
#4 Updated by Galya B over 1 year ago
How might you test this bug?
#5 Updated by Artur Școlnic over 1 year ago
Apart from the example in note 1, I have not been able to find cases where errors are not logged, but there might be. If you run the example in note 1, the apperror will be logged in the file.log in 4GL, in FWD it is not.