Bug #7236
Inconsistencies in stderr and logs related to MESSAGE and AppError constructor
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/30/2023
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
Related issues
History
#1 Updated by Galya B about 1 year ago
To be addressed after the merge of #5701, #5753 and #5703.
Steps to reproduce in #5701#note-86.
Issues:- The error message from
AppError
constructor is printed twice to System.err / logs (could be related toAddMessage
). MESSAGE
is sometimes printed twice and sometimes not at all (tested in the context ofOUTPUT TO
).MESSAGE
withoutVIEW-AS ALERT-BOX
in the context ofOUTPUT TO
is not logged to LOG-MANAGER, but seems to be written to appserver logs in OE.- Concatenating strings by just placing them one after another as arguments to
MESSAGE msg1 msg2 VIEW-AS ALERT-BOX ERROR
adds a whitespace between the strings in OE, but not in FWD.
#2 Updated by Galya B about 1 year ago
- Related to Bug #5703: rationalize, standardize and simplify the client-side log file name configuration added
#4 Updated by Galya B about 1 year ago
- Related to Bug #5701: logfile names for -O outputToFile use the spawner pid instead of the Java (FWD client process) pid added
#5 Updated by Galya B about 1 year ago
- Subject changed from Inconsistencies in stdout and logs related to MESSAGE and AppError constructor to Inconsistencies in stderr and logs related to MESSAGE and AppError constructor