pinpoint-apm/pinpoint · warning

BufferMetric initialize fail: {}

Error message

BufferMetric initialize fail: {}

What it means

BufferMetricProvider logs this warning when reflective creation of the configured BufferMetric class fails with a ReflectiveOperationException, then returns BufferMetric.UNSUPPORTED_BUFFER_METRIC. The metric layer keeps running but buffer statistics are reported as unsupported. It is a graceful-degradation path, not a crash.

Source

Thrown at agent-module/profiler/src/main/java/com/navercorp/pinpoint/profiler/context/provider/stat/buffer/BufferMetricProvider.java:57

    @Override
    public BufferMetric get() {
        BufferMetric bufferMetric = createBufferMetric(BUFFER_METRIC);
        logger.info("loaded : {}", bufferMetric);
        return bufferMetric;
    }

    private BufferMetric createBufferMetric(String classToLoad) {
        if (classToLoad == null) {
            return BufferMetric.UNSUPPORTED_BUFFER_METRIC;
        }
        try {
            @SuppressWarnings("unchecked")
            Class<BufferMetric> bufferMetricClass = (Class<BufferMetric>) Class.forName(classToLoad);
            Constructor<BufferMetric> bufferMetricConstructor = bufferMetricClass.getConstructor();
            return bufferMetricConstructor.newInstance();
        } catch (ReflectiveOperationException e) {
            logger.warn("BufferMetric initialize fail: {}", classToLoad);
            return BufferMetric.UNSUPPORTED_BUFFER_METRIC;
        }
    }
}

View on GitHub (pinned to 744c3d3075)

Solutions

1. Read the chained ReflectiveOperationException to see whether the class was not found or the constructor was missing
2. Verify the agent jar is intact and contains the expected buffer metric classes (e.g. DefaultBufferMetric)
3. If the JVM genuinely lacks the buffer-pool MBeans, accept the UNSUPPORTED_BUFFER_METRIC fallback — buffer metrics are simply not collectible on that platform
4. Upgrade/downgrade Pinpoint agent to a version supporting the target JVM

Class<?> c = Class.forName("com.navercorp.pinpoint.profiler.context.provider.stat.buffer.BufferMetricProvider"); // plus verify agent jar integrity: jar tf pinpoint-agent.jar | grep BufferMetric

try { return bufferMetricConstructor.newInstance(); } catch (ReflectiveOperationException e) { logger.warn("BufferMetric initialize fail: {}", classToLoad); return BufferMetric.UNSUPPORTED_BUFFER_METRIC; }

When it happens

Trigger: Class.forName fails for the buffer metric class name derived from the JVM/version, or the class has no public no-arg constructor, or instantiation throws.

Common situations: Running an unusual or newer JVM where the expected MBean buffer pool metric class is absent; agent jar is partially deployed/instrumentation stripped; package rename between Pinpoint versions.

Related errors

• Error creating ShutdownHookRegister [{}]
• Unknown CpuLoadMetric : {}
• Error creating CpuLoadMetric [{}]
• Unknown FileDescriptorMetric : {}
• Error creating FileDescriptorMetric [{}]

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