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 analyze this issue carefully:
- gRPC's
ManagedChannelImpllog messages contain unsubstituted placeholders{0},{1}etc. - This is because gRPC uses
java.util.logging(JUL) withMessageFormat-style placeholders, and the bridge to SLF4J/Logback isn't translating these properly. - The suggested fix is to install
SLF4JBridgeHandler(org.slf4j:jul-to-slf4j) and ensure it translates JULLogRecord.parametersviaMessageFormat.format(...)before delegating to SLF4J.
Let me first explore the repository structure to understand the codebase, then find the logging configuration/bridge code.
- gRPC's
Assistant
Let me search more specifically for the logging bridge configuration and SLF4J bridge handler.
Assistant
Let me look at the core logging infrastructure and the relevant pom files
Assistant
Let me look at the core logging infrastructure one by one
Assistant
Let me look at the Logger interface and DefaultLogger, and also the AnsiLogFormatter.
Assistant
Now I need to find the key files. Let me look at the DefaultLogger.
Assistant
Now let me look at the AnsiLogFormatter (the JUL formatter that formats logs) and the log properties:
Assistant
Let me look at the build dependencies to understand the logging stack
Assistant
Let me look at the root pom.xml for dependencies and then the LogFormatter
Assistant
So they use
slf4j-jdk14! That's the SLF4J binding that routes SLF4J calls tojava.util.logging. Andlogback-classicis also there.Let me check the full dependencies more:
Assistant
Let me check the server pom.xml and ha-raft pom.xml for more logging and gRPC dependencies
Assistant
Let me look at the LogFormatter class
Assistant
Let me check how logback is used and what the server's actual logging setup
Assistant
Let me check the FixedGrpcLogAppender that's mentioned in the issue description
Assistant
Let me look at the arcadedb-log.properties
Assistant
Let me create a script to reproduce the issue
Assistant
Let me compile and run the reproduce script
Assistant
Interesting! With JUL's default
SimpleFormatter, the parameters ARE correctly substituted becauseSimpleFormatter.formatMessage()callsMessageFormat.format(). The issue is that ArcadeDB replaces the formatter with its ownAnsiLogFormatterandLogFormatter, which useString.format()instead ofMessageFormat.format().Let me confirm by testing with the ArcadeDB formatter:
Assistant
Let me check if the engine module is compiled
Assistant
Let me compile the engine module
Assistant
Good. Now let me run the reproduce script:
Assistant
I've confirmed the issue! The output shows
[{0}] Failed to resolve name. status={1}without substitution. The problem is in bothLogFormatter.customFormatMessage()andAnsiLogFormatter.customFormatMessage()- they useString.format()which doesn't understandMessageFormat-style placeholders.Let me check the relevant source files and apply the fix:
Assistant
Let me use the proper command to open files.
Assistant
Now let me edit the LogFormatter to handle MessageFormat-style placeholders:
Assistant
Let me use the open and edit commands properly. Let me first open the file.
Assistant
Now let me edit the LogFormatter to handle MessageFormat-style placeholders:
Assistant
Now add the helper methods before the closing brace
Assistant
I see there's a duplicate line. Let me fix that:
Assistant
Now let me fix the
AnsiLogFormattersimilarly. Let me open itAssistant
Now let me fix the AnsiLogFormatter. Since it extends LogFormatter, it will inherit the helper methods:
Assistant
Now let me recompile and test the fix:
Assistant
Now let me re-run the reproduce script to verify the fix
Assistant
The fix works! Now let me also test that the
LogFormatter(file formatter) works correctly and thatString.format()-style messages still work:Assistant
All tests pass. Let me now run the existing LoggerTest and any other relevant tests:
Assistant
Let me check the LoggerTest.
Assistant
Let me run the LoggerTest
Assistant
All LoggerTest tests pass. Let me also run some broader tests to make sure nothing is broken:
Assistant
Let me check if there are any other formatters in the codebase that might need the same fix
Assistant
Let me review my changes to make sure everything is clean
Assistant
Let me also test edge cases to ensure robustness
Assistant
All edge cases are handled well. Let me verify the final state of my changes:
Assistant
Let me verify the AnsiLogFormatter as
Assistant
Let me clean up the temp files and run a broader test compilation:
Assistant
Let me also check the GrpcLoggingInterceptor to see if it's relevant
Assistant
Let me verify there are no other formatters that might need the fix
Assistant
Let me also check if there's any SLF4J bridge handler configuration
Assistant
No SLF4JBridgeHandler or jul-to-slf4j is used anywhere. Let me now run the engine test suite to make sure nothing is broken
Assistant
The full test suite takes too long. Let me run just the key tests.
Assistant
All tests pass. Let me now submit 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 →