The timestamp is not wrong, it is being reported in Greenwich Mean Time (GMT) format.
This is working as expected due to a change that was made in OpenEdge 11.2.1 and later with regards to how the Progress Signal Handler shows the timestamp header in Greenwich Mean Time (GMT) format.
Library functions to do conversion to local time are not async signal safe. This change in timestamp formatting allows OpenEdge to avoid calling certain UNIX system functions which can cause a process to hang or not properly terminate when called from within the Signal Handler code.
During regular execution, when OpenEdge processes write to the database log file (.lg) the timestamp header of the message shows the time in local time format. This header with local time information includes the offset of the local time from Greenwich Mean Time (GMT):
[2019/08/27@14:42:46.806+0200] - which shows that the time is 2 hours offset from GMT.
On UNIX systems, when OpenEdge processes exceptions (either internal fatal errors or signals from other processes), messages may be written to the database log (.lg) file from within the process' Signal Handler code. These messages when written from the Signal Handler, show a timestamp header in Greenwich Mean Time (GMT) format.
[2019/08/27@12:42:46.000+0000] -which shows that the time is actual GMT with 0 hours offset. In addition, the time information written from the process' Signal Handler does not show milliseconds.
This change in timestamp formatting allows OpenEdge to avoid calling certain UNIX system functions which can cause a process to hang or not properly terminate if called from within the Signal Handler code.
