gRPC ManagedChannelImpl log messages contain unsubstituted placeholders Affected…
- User
gRPC ManagedChannelImpl log messages contain unsubstituted placeholders Affected version: ArcadeDB server 26.4.2 Component: logging — bridge between gRPC's java.util.logging and the server's SLF4J/Logback backend
Summary
Some WARNING messages emitted by gRPC's ManagedChannelImpl are written to the ArcadeDB server log with the original MessageFormat placeholders ({0}, {1}) left literal instead of being substituted with the actual values.
Example
2026-05-21 06:53:11.234 WARNI [ManagedChannelImpl] [{0}] Failed to resolve name. status={1} 2026-05-21 06:53:11.234 WARNI [ManagedChannelImpl] [{0}] Failed to resolve name. status={1}
Expected (illustrative):
WARNI [ManagedChannelImpl] [channel-7] Failed to resolve name. status=UNAVAILABLE: Unable to resolve host vcc-superx-arcadedb-2.…
Root cause (suspected)
gRPC's internal loggers use java.util.logging with MessageFormat-style placeholders. The bridge that forwards JUL records to the ArcadeDB logging backend (SLF4J/Logback) is not translating {0}, {1} parameters into the SLF4J {} style, so the parameter array is dropped and the raw template ends up in the log file. Confirmation: the same logical event is also logged elsewhere (via GrpcLogAppender / AppendLogResponseHandler) with the full formatted message, so the data exists — it's just lost on the ManagedChannelImpl path.
Impact
Low severity but operationally annoying — these log lines carry zero information, so anyone scanning logs for the actual channel and gRPC status gets a stream of [{0}] Failed to resolve name. status={1} that they then have to correlate with neighbouring lines.
Suggested fix
Either:
- Install SLF4JBridgeHandler (org.slf4j:jul-to-slf4j) and ensure it translates JUL LogRecord.parameters via MessageFormat.format(...) before delegating to SLF4J; or
- Configure a JUL Handler for the io.grpc logger that uses a SimpleFormatter-compatible formatter so parameters are substituted before the message reaches the SLF4J side.
Environment
- ArcadeDB 26.4.2, default packaging
- Logs viewed via kubectl logs; same behaviour observed across all 3 HA pods
Interface
No new interfaces are introduced.
- Assistant
Investigating the JUL-to-SLF4J logging bridge and how gRPC log messages are forwarded.
- Assistant
Root cause:
LogFormatterandAnsiLogFormatteruse printf-styleString.formatted(), but gRPC's JUL loggers useMessageFormatplaceholders ({0},{1}). Fixing both formatters and adding a regression test. - Assistant
MessageFormat leaves printf-style templates unchanged; detecting placeholder style before formatting.
- Assistant
Fixed. gRPC's
ManagedChannelImpllogs through JUL withMessageFormatplaceholders ({0},{1}), but ArcadeDB's formatters were using printf-styleString.formatted(), which leaves those placeholders literal.Root cause
LogFormatterandAnsiLogFormatterformattedLogRecordparameters with:message.formatted(additionalArgs) // printf style: %s, %dJUL libraries like gRPC pass the template and arguments separately and expect
MessageFormat.format(message, parameters). ArcadeDB's ownDefaultLoggerpre-formats messages before calling JUL, so this only affected third-party JUL loggers.Fix
Added
formatMessageWithParameters()inLogFormatterthat:- Uses
MessageFormat.format()when the message contains{0},{1}, etc. - Falls back to printf-style
String.formatted()otherwise
Both
LogFormatter(file logs) andAnsiLogFormatter(console logs) now use this helper.Verification
Added
LogFormatterTestwith regression cases for:- gRPC-style MessageFormat placeholders (the reported bug)
AnsiLogFormatterpath- Messages without parameters
- printf-style fallback
cd engine && mvn test -Dtest=LogFormatterTest,LoggerTestAfter upgrade, the log line should look like:
WARNI [ManagedChannelImpl] [channel-7] Failed to resolve name. status=UNAVAILABLE: Unable to resolve host ...instead of
[{0}] Failed to resolve name. status={1}. - Uses
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →