Skip to content
TheChatArchiveThe Chat Archive
gpt-5.6-sol· openaiHugging 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 trace the JUL-to-ArcadeDB logging path, add a focused regression test for parameterized LogRecords, then implement and run the relevant test suite.

  3. Assistant

    rg isn’t installed in this checkout, so I’m using targeted find/grep searches instead.

  4. Assistant

    The fault is in ArcadeDB’s two JUL formatters: both read LogRecord.getMessage() and apply Java String.formatted, while JUL requires Formatter.formatMessage(record) for {0} parameters and resource bundles. I’m correcting both console and file formatter paths and covering each with regression tests.

  5. Assistant

    The initial Maven invocation reached an uncached test-runner dependency, so I stopped it and am rerunning strictly offline. Compilation had already completed successfully.

  6. Assistant

    Both production code and the new regression test compile offline. The normal test runner itself is unavailable in the local Maven cache, so I’m validating the exact runtime formatting path directly against the compiled classes as an additional check.

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