pinpoint-apm/pinpoint · warning

Failed to send agentInfo. request unsuccessful, response={}

Error message

Failed to send agentInfo. request unsuccessful, response={}

What it means

Same unsuccessful-result path as error 586, logged in the fallback branch where agentInfo or getAgentInformation() is null, so only the collector's response message is included. Send returns false and is retried.

Source

Thrown at agent-module/profiler/src/main/java/com/navercorp/pinpoint/profiler/AgentInfoSender.java:193

            try {
                agentInfo = agentInfoFactory.createAgentInfo();

                logger.info("Sending AgentInfo={}", agentInfo);
                CompletableFuture<ResultResponse> future = dataSender.request(agentInfo);
                ResultResponse result = future.get(3000, TimeUnit.MILLISECONDS);
                if (result == null) {
                    if (agentInfo != null && agentInfo.getAgentInformation() != null) {
                        logger.warn("Failed to send agentInfo={}. result not set", agentInfo.getAgentInformation());
                    } else {
                        logger.warn("Failed to send agentInfo. result not set");
                    }
                    return false;
                }
                if (!result.isSuccess()) {
                    if (agentInfo != null && agentInfo.getAgentInformation() != null) {
                        logger.warn("Failed to send agentInfo={}. request unsuccessful, response={}", agentInfo.getAgentInformation(), result.getMessage());
                    } else {
                        logger.warn("Failed to send agentInfo. request unsuccessful, response={}", result.getMessage());
                    }
                }
                return result.isSuccess();
            } catch (ExecutionException ex) {
                logError(agentInfo, ex.getCause());
            } catch (InterruptedException ex) {
                Thread.currentThread().interrupt();
                logError(agentInfo, ex);
            } catch (TimeoutException ex) {
                logError(agentInfo, ex);
            }
            return false;
        }

        private void logError(AgentInfo agentInfo, Throwable cause) {
            if (agentInfo != null && agentInfo.getAgentInformation() != null) {
                logger.warn("Failed to send agentInfo={}", agentInfo.getAgentInformation(), cause);
            } else {

View on GitHub (pinned to 744c3d3075)

Solutions

1. Fix the missing AgentInformation first (see configuration checks for error 585)
2. Inspect the collector response message in the log for the rejection cause
3. Check collector logs/storage health around the same timestamp
4. Ensure agent/collector protocol versions match

if (agentInfo == null || agentInfo.getAgentInformation() == null)
    throw new IllegalStateException("AgentInformation missing");

if (!result.isSuccess()) { logger.warn("Failed to send agentInfo. request unsuccessful, response={}", result.getMessage()); return false; }

When it happens

Trigger: ResultResponse.isSuccess() == false returned while agentInfo or its AgentInformation is null — a combination of a collector-side rejection and missing agent metadata.

Common situations: Programmatic/builder misuse where AgentInfo lacks AgentInformation combined with collector rejecting the request; extremely early startup where agent info is not yet populated.

Related errors

• Failed to send agentInfo={}. result not set
• Failed to send agentInfo. result not set
• Failed to send agentInfo={}. request unsuccessful, response=
• Failed to send agentInfo={}
• Failed to send agentInfo

AI-assisted analysis of pinpoint-apm/pinpoint@744c3d3075 (2026-09-07). Data as JSON: /api/errors/108b3aa1dda5ed84. Report an issue: GitHub.