ISSUE DESCRIPTION gRPC ManagedChannelImpl log messages contain unsubstituted…
- User
ISSUE DESCRIPTION
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
ADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /arcadedb, current file: none) bash-$
- Assistant
I’ll first locate the JUL-to-server logging bridge and relevant tests/dependencies, then reproduce the formatting loss at the smallest useful scope before implementing and validating a general fix.
- Assistant
The server installs a custom
java.util.logging.LogManager, so the defect is more likely in that manager/logger forwarding path than in Logback configuration. I’ll inspect it together with ArcadeDB’s core log manager and formatter implementations to identify whereLogRecordparameters disappear. - Assistant
Both configured JUL formatters explicitly access the parameter array. I’ll compare their formatting logic and inspect the core logging API’s placeholder convention; this should reveal whether they assume
String.format(%s) while gRPC suppliesMessageFormat({0}). - Assistant
The reproduction is evident in both formatters: they call
String.formatted, which only understands printf placeholders, so a JUL record with[{0}]remains unchanged. A naïve switch to inheritedFormatter.formatMessagewould fix JUL/gRPC but break ArcadeDB’s many%smessages. I’ll inspect howDefaultLoggerconstructs records and quantify conventions so the shared formatter can preserve native behavior while correctly honoring JUL semantics. - Assistant
ArcadeDB intentionally emits printf templates through JUL, while third-party JUL libraries follow
MessageFormat. The robust compatibility rule is therefore: use standard JULFormatter.formatMessage(record)when it actually transforms a parameterized message; otherwise retain ArcadeDB’s printf fallback. I’ll inspect exact record construction and existing logger tests, then centralize this rule inLogFormatterso ANSI and plain output cannot diverge. - Assistant
DefaultLoggerpreformats ArcadeDB messages before creating JUL records, confirming that standard JUL formatting is safe for normal server logs. I’ll nevertheless retain the formatter’s legacy printf support for direct parameterized records as a fallback. The shared algorithm will first apply JUL’s built-in resource-bundle/MessageFormatsemantics, and only when JUL leaves the template untouched will it tryString.formatted; both console and file formatters will call it. - Assistant
Python is unavailable in this environment, so no files were changed. I’ll apply the same focused edits with the repository’s patch tooling, then inspect the resulting diff.
- Assistant
The shell also lacks
apply_patch; I’ll use the provided editor commands. I’ll make the plain formatter changes first, then the ANSI formatter. - Assistant
I’ll replace the parameter handling block and add the compatibility formatter method immediately before the requester-name helper.
- Assistant
The shared method is in place; I noticed only a cosmetic missing blank line before the next method and will fix that while converting the ANSI formatter to use the shared result.
- Assistant
The diff now routes both configured handlers through one JUL-compliant implementation and retains malformed/printf fallback behavior. I’ll compile the engine and run the existing
LoggerTest, which exercises logging initialization and both configured formatter classes indirectly. - Assistant
The Maven wrapper failed before compilation because this sandbox has no
HOMEvariable; this is an environment issue, not a code/test failure. I’ll rerun with a temporary Maven home explicitly set and use the normal targeted test command. - Assistant
Compilation and all four existing logger tests pass. I’ll now run a temporary, non-repository regression harness that constructs the same
LogRecordshape gRPC uses, verifies both file and ANSI formatter output, and checks compatibility edge cases: printf fallback, parameterless literal braces, and invalid printf syntax. - Assistant
The targeted reproduction now passes for the exact gRPC template in both output paths, and compatibility cases behave correctly. One additional defensive edge is a JUL record with a null message plus parameters: uncommon and already poorly handled, but the new shared method can cheaply avoid dereferencing null. I’ll add that guard, recompile, and rerun the harness.
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
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →