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
Let me start by understanding the repository structure and finding the relevant code that deals with JUL (java.util.logging) to SLF4J bridging. The issue is about gRPC's
ManagedChannelImpllog messages containing unsubstituted placeholders like{0},{1}because the JUL-to-SLF4J bridge doesn't translatejava.util.loggingMessageFormat-style placeholders to SLF4J's{}style.Let me explore the repository structure first.
Assistant
Let me narrow the search to find the specific logging infrastructure. The issue mentions
java.util.loggingandManagedChannelImpl. Let me look at the logging-relatedAssistant
Let me run a single command to find the relevant logging infrastructure.
Assistant
Let me look at the key logging infrastructure files and search for relevant terms like "SLF4JBridgeHandler", "MessageFormat", or "jul" more
Assistant
Let me look at the key logging files in
Assistant
Let me use the open command properly via bash_terminal.
Assistant
Let me scroll down to see the logging methods.
Assistant
Let me continue scrolling.
Assistant
Let me scroll further.
Assistant
Let me look at the LogFormatter and AnsiLogFormatter to understand how JUL log records are formatted.
Assistant
Let me check the AnsiLogFormatter and AnsiCode class to understand the full
Assistant
Now let me also check the Logger interface to understand the full API:
Assistant
Let me look at the existing LoggerTest to understand the testing infrastructure
Assistant
Now I have a clear understanding of the problem. Let me create a small test script to reproduce the issue first, then fix the formatters.
Assistant
Now let me compile and run this test.
Assistant
Now I've confirmed the issue. The fix needs to handle both
{0},{1}style (MessageFormat) and%s,%dstyle (printf/String.formatted()). Let me implement the fix in both formAssistant
Now let me fix the AnsiLogFormatter as well
Assistant
Now fix the AnsiLogFormatter:
Assistant
Let me verify the imports are correct and check the final state of both files:
Assistant
Let me check if there are any other formatters or logging-related files that might have similar
Assistant
The fix is complete. Let me now run the existing tests to make sure nothing is broken.
Assistant
Let me try to compile and run the LoggerTest to verify the changes don't break anything:
Assistant
Good, compilation succeeds. Let me run the LoggerTest:
Assistant
All existing tests pass. Now let me create a quick end-to-end test to verify the fix works with a simulated JUL log record:
Assistant
Now let me compile and run this test:
Assistant
All tests pass perfectly. Let me clean up the temporary test files and verify the final diff:
Assistant
The changes look clean. Let me also run a broader set of tests in the engine module to make sure nothing is broken
Assistant
The test suite for the full engine module times out, but the specific
LoggerTest(4 tests) passed. Let me do a final review of the changes:
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 →