#29383 A dead SOCKET_APPENDER (Chainsaw, localhost:4445) in the default logging configuration can cause logging to stall and operations to abort under heavy load

enhancement

critical

#29088

Model-based access rights

#29108

Lightweight UI definition layer (TL Views) based on React UI components

major

#28694

Description of model parts as formatted text (rich text)

#28708

Enable Standard Selection in (Tree) Tables and Grids via TL Script

#29102

Add com.top_logic.layout.react module for React/SSE integration

#29221

Automatic determination of possible authorization configurations

#29349

XML Parsing Functions for TL-Script via XMLImporter

#29374

TL Script: gzip()

#29389

Code Completion for Variables ($) in the TL Script Editor

#29396

Conversation display for TL Views: object list element, file chips, card panels

#29399

Info Service Notifications: Display at the bottom instead of the top, and keep them in place when hovering over them with the mouse

#29400

Introduce a first-class "operation mode" service for applications (OperationMode enum + ApplicationModeService)

minor

#29085

Re-login on session timeout instead of redirect to login page

#29089

Extend the TL Script functions log() and info() to include selectable message levels (INFO, WARN, ERROR)

#29195

Problems with HTML attributes and TL script

#29306

TL Script: dateFormat() should accept an explicit timezone to format Calendar values losslessly

#29382

Expose a public, classpath-driven overload of `Workspace.getAppPaths`

#29385

The app archetype should automatically generate a standard git-ignored local-credentials overlay (tl_config) by default

#29392

Transaction Abort on Non-2xx Response

#29398

defect

major

#29383

A dead SOCKET_APPENDER (Chainsaw, localhost:4445) in the default logging configuration can cause logging to stall and operations to abort under heavy load

#29384

The TL-Script functions `resetSequence` and `generateSequenceId` generate a different sequence ID than `SequenceDefaultProvider` (in terms of suffix and context order), so they cannot reset a provider-managed sequence with a dynamic context

#29394

Editable tables in the React UI: Generalized row-set bindings for tabular editing in forms

#29410

Attribut filename der Structured-Text-Bildablage case-sensitive (binär) speichern

#29419

Understandable save failures and form validation feedback in the React view layer

minor

#28816

Reference value attributes only generate errors with SingleSelection

#29359

Inappropriate tooltips on some main tabs

#29360

Occasional error message in the log: "mainLayout" is null.

#29361

Invalid database definition for tag

#29363

Missing validation of dialogs in GOTO statements to dialogs of invisible parents

#29380

Context-sensitive auto-numbering fails if the context and the numbered object are created within a single transaction

#29381

Double-clicking in a graphic component does not work reliably

#29390

Subtree selection ends too early if the lowest level is not included in the level filter

#29393

URL routing in the React view layer is broken: ForwardingReactContext does not delegate getRouteManager()

#29401

Images in an image drop zone cannot be copied or saved using the browser's context menu

#29402

Tree selection is lost when the view is refreshed (invalidated)

#29412

Flaky TestDynamicComponentService.testIncrementalUpdates: asserts on asynchronous WatchService event after a fixed 10ms sleep

#29416

Anzeige des Änderungslogs schlägt fehl, wenn parallel Änderungen committet werden

#29420

FlowDiagram: Fehlerfall im row-wise Sub-Grid: subGridCols=2 und subGridStartCol=1

#29426

FlowDiagram: Text in PDF-eingebettetem Diagramm ist nicht selektierbar

task

major

#29407

Security-Scan: npm-Abhängigkeiten der React-Module aktualisieren

#29408

Security-Scan: httpcore5 anheben; pdfbox-/azure-Findings bewerten

minor

#29415

Slim down the repository CLAUDE.md and consolidate developer guidance into skills and FAQ articles

defect

major

#29383

A dead SOCKET_APPENDER (Chainsaw, localhost:4445) in the default logging configuration can cause logging to stall and operations to abort under heavy load

Migration

The default logging configuration (tl-core, WEB-INF/conf/logging/default.xml) defines a log4j2 Socket appender named SOCKET_APPENDER that targets localhost:4445 (intended for a Chainsaw dev receiver). It is controlled by the tl_developerMode=true SystemPropertyArbiter and referenced from <Root>, so in developer mode, every logged event is routed to it.

When no receiver is listening on port 4445 (which is usually the case in developer mode), log4j’s TcpSocketManager maintains a background Reconnector and buffers writes to the unreachable endpoint. Under a burst of log messages, the socket’s send buffer fills up. Because the framework runs under log4j’s AwaitCompletionReliabilityStrategy, the logging call then blocks and/or throws an AppenderLoggingException from within Logger.info(...). Two consequences:

The entire logging pipeline stalls—the FILE_APPENDER stops receiving events, so top-logic.main.log freezes while the application continues to run.
The failure propagates into the calling application code that issued the log call.

Observed impact: a long-running background operation that reported progress via the TL-Script log(...) function (~3,200 messages within a few seconds) experienced a break in its logging pipeline; the main log froze mid-run, and the operation aborted silently at a clean batch boundary. Abbreviated stack trace:

org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to TCP:localhost:4445: socket not available
    at org.apache.logging.log4j.core.net.TcpSocketManager.write(TcpSocketManager.java:264)
    at org.apache.logging.log4j.core.appender.SocketAppender.directEncodeEvent(SocketAppender.java:598)
    at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(...)
    at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:92)
    at org.apache.logging.log4j.core.Logger.log(Logger.java:187)
    at com.top_logic.basic.Logger.info(Logger.java:174)

A dead/optional dev appender must never be able to stall file/console logging or cause the application to fail. Requested fix (any of):

Remove SOCKET_APPENDER from the default configuration; or
Make it robust: set ignoreExceptions="true", wrap it in an Async appender, and/or only enable it when a receiver on port 4445 is actually reachable.

Workaround in an application: override WEB-INF/conf/logging/default.xml and remove the SOCKET_APPENDER appender definition and its <Root> AppenderRef.

Migration

Developers who forward log events to an external log viewer (e.g., Chainsaw listening on localhost:4445) must now explicitly enable the SOCKET_APPENDER: add

-Dtl_logReceiver=true

to the VM arguments of the launch configuration. Developer mode (tl_developerMode=true) alone no longer activates the appender. The host, port, and serialized event format remain unchanged. Developers who do not run a log receiver do not need to make any changes—the appender is no longer part of their logging configuration.

Note for users who have opted in: the appender runs with `ignoreExceptions="true"`; while no receiver is reachable, events destined for the socket are dropped silently—file and console logging are unaffected.