Skip to content
TheChatArchiveThe Chat Archive
composer-2.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

gRPC ManagedChannelImpl log messages contain unsubstituted placeholders Affected…

  1. 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.

  2. Assistant

    I'll investigate how ArcadeDB bridges gRPC's java.util.logging output to SLF4J and why MessageFormat placeholders aren't being substituted.

  3. Assistant

    Root cause: LogFormatter and AnsiLogFormatter use String.formatted() for JUL parameters, but gRPC uses MessageFormat-style {0} placeholders. I'll fix both formatters and add a regression test.

  4. Assistant

    Fixed. The issue was in ArcadeDB's JUL formatters, not a missing jul-to-slf4j bridge.

    Root cause

    ArcadeDB uses java.util.logging end-to-end. LogFormatter and AnsiLogFormatter formatted LogRecord parameters with String.formatted(), which expects %s-style placeholders. gRPC's ManagedChannelImpl logs via JUL with MessageFormat placeholders ({0}, {1}). When String.formatted() failed, the formatters fell back to the raw template, producing lines like:

    [{0}] Failed to resolve name. status={1}
    

    Fix

    Added formatMessageWithParameters() in LogFormatter that:

    1. Detects MessageFormat-style {0} placeholders and uses MessageFormat.format()
    2. Falls back to String.formatted() for %s-style messages
    3. Returns the raw message if both fail

    AnsiLogFormatter now delegates to the same helper.

    Verification

    Added LogFormatterTest with a regression test mirroring the gRPC ManagedChannelImpl warning pattern. All tests pass:

    • LogFormatterTest (new)
    • LoggerTest (existing)

    After this change, the example log line should render as:

    WARNI [ManagedChannelImpl] [channel-7] Failed to resolve name. status=UNAVAILABLE: Unable to resolve host ...
    

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.