TopLogic - the automated application engine
  • Releases
  • Dokumentation
  • Github
  • Discord
  1. Home
  2. Releases
  3. TL_7.5.0-M5
  4. #27032

7.5.0-M5
TopLogic Release

2022-11-02

Enhancement

Major
#26644
Kafka and TL-Sync should use an exponential backoff in case of problems
Detail
#26966
Configuring StorageMapping on PrimitiveStorage
#27006
Add tooltip description for LoginMessage interval attribute.
#27008
Enable tooltips via tabs
#27011
Update Maven Sources plugin to version 3.3.0
#27024
Support for multi-file upload in declarative forms

Bugfix

Major
#26930
Long values lead to unusable column filters
#26968
Missing items in refetch update event
Detail
#26970
Wrong DB configuration at replay after changing FastList table
#26989
Broken GWT Launch Config
#26993
Application monitor uses wrong locale for displaying working memory values
#27012
Potential NullPointerException with Drag&Drop
#27021
Missing search buttons in Modern theme
#27022
Cyclic FileSystemProvider dependency in Log4J2
#27025
Inconsistent font type and size for number fields
#27026
Creating company contact: Half of the values are not saved
#27030
SafeHTML not started during automatic data migration
#27031
Missing adaptation of the stored model in model changing EventRewriter
#27032
Unexpected order of backup log files with Log4j2
#27036
The ThemeImage "NoIcon" does not disappear, but is displayed as an empty white image
#27039
Administration: Contact cleanup produces error message
#27040
Jackson FasterXML Update to 2.13.4
#27043
Batik update to 1.16
#27045
Maintenance page ScanData.jsp does not compile in openJDK 1.8
Bugfix

Detail

#27032

Unexpected order of backup log files with Log4j2

Logging

Top-Logic has a default log configuration file for Log4j2.

Log files are only filled up to a certain size and then "backed up". Only a certain amount (10) of backup files are kept. Older backup files are deleted.

When naming the backup files, an unexpected strategy is used: tl.main.log -> tl.main.10.log -> tl.main.9.log -> ...-> tl.main.1.log, i.e. if tl.main.log is full, tl.main.2.log will be renamed to tl.main.1.log (overwriting), tl.main.3.log will be renamed to tl.main.2.log (overwriting),...,tl.main.log will be renamed to tl.main.10.log (overwriting) and then tl.main.log will be recreated. I.e. tl.main.10.log is the newest backup file and tl.main.1.log is the oldest.

Intuitively, one would expect tl.main.1.log to be the newest backup file and tl.main.10.log to be oldest.

The default configuration file is changed to this.

Test

  • Make changes until at least 2 backup files are created.
    • Expectation: The file top-logic.main.1.log is newer than top-logic.main.2.log.
  • Get Started
  • Github
  • Discord
  • Das Unternehmen hinter TopLogic
  • Softwareentwicklung heute
  • Kontakt

© Copyright – Business Operation Systems GmbH

  • top-logic.com
  • Nutzungsbedingungen
  • Impressum
  • Rechtlicher Hinweis
  • Datenschutz
  • DE
  • Login