Defective "ELAPSED-TIME" lines in pc_server log
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
The pc_server log sometimes has lines like this:
ELAPSED-TIME: C0511 2017-04-25 11:14:15 22  [log] version 22.01 format ALEPH compression 3 encryption 0
This is different than the other "ELAPSED-TIME" lines in the log and seems messed up.
This is a defect in the pc_server logging process. A standard transaction "ELAPSED-TIME" line looks like this:
ELAPSED-TIME: C0121 15:25:38 0.0087
A standard "version" line looks like this:
2017-04-26 12:32:25 56  [log] version 23.01 format ALEPH compression 3 encryption 0
It seems like the version line for one transaction has overwritten the last part of the previous transaction's ELAPSED-TIME line. It seems that this can happen when the pc_server is very busy.
Though this is unsightly and confusing, we have found that it is *not* associated with any real problem with data, updates, etc.
- Article last edited: 6-Apr-2017