Bug #7462
fix 'AS' instead of '4GL' in LOG-MANAGER log lines and add an incompatible FWD and FWD-AS for 4GL and AS texts
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
Related issues
History
#1 Updated by Constantin Asofiei 11 months ago
- Related to Feature #3853: implement LOG-MANAGER runtime added
#2 Updated by Constantin Asofiei 11 months ago
When used on 4GL client, LOG-MANAGER outputs this:
[23/06/22@17:39:10.142+0300] P-003276 T-003280 1 4GL -- Logging level set to = 2 [23/06/22@17:39:10.142+0300] P-003276 T-003280 1 4GL -- No entry types are activated [23/06/22@17:39:10.142+0300] P-003276 T-003280 1 4GL APPL abc
for this code:
log-manager:logfile-name = "a.txt". log-manager:write-message("abc").
When used with appserver, the log lines are these:
[23/06/22@17:41:23.713+0300] P-004380 T-004376 2 AS AS Application Server connected with connection id: 192.168.0.136::catest::4090::085ad9a485f0092e:-61441c55:188e38c9200:-7fdf. (8358) [23/06/22@17:41:23.713+0300] P-004380 T-004376 1 AS APPL abc [23/06/22@17:41:23.714+0300] P-004380 T-004376 2 AS AS Application Server disconnected with connection id: 192.168.0.136::catest::4090::085ad9a485f0092e:-61441c55:188e38c9200:-7fdf. (8359)
Note how 'AS' is used instead of '4GL'. This needs to be fixed so we are compatible.
In addition, we can provide an incompatible mode, where:- instead of '4GL', we use 'FWD'
- instead of 'AS', we use 'FWD-AS'
This incompatible configuration would be somewhere in directory.xml (not sure yet what section is appropriate).
#4 Updated by Constantin Asofiei 11 months ago
OK, sorry about that. I keep forgetting that LOG-MANAGER needs more work.