value of disable property is not false, pinpoint.disable=tru

Error message

value of disable property is not false, pinpoint.disable=true

What it means

PinpointStarter.start() re-checks the loaded pinpoint.config for the pinpoint.disable property; if it is set to true, it logs this warning and returns false, aborting agent startup. Unlike the premain-level Env check, this one is driven by the config file itself.

Source

Thrown at agent-module/bootstraps/bootstrap/src/main/java/com/navercorp/pinpoint/bootstrap/PinpointStarter.java:86

        }
        BootLogger moduleLogger = BootLogger.getLogger(ModuleBootLoader.class);
        moduleLogger.info("java-module detected");
        moduleLogger.info("ModuleBootLoader start");

        ModuleBootLoader moduleBootLoader = new ModuleBootLoader(instrumentation, parentClassLoader, moduleLogger::info);
        moduleBootLoader.loadModuleSupport();
        return moduleBootLoader;
    }



    boolean start() {

        try {
            final Properties properties = loadProperties();

            if (DisableOptions.isDisabled(properties::getProperty, DisableOptions.CONFIG)) {
                this.logger.warn("value of disable property is not false, pinpoint.disable=true");
                return false;
            }

            // this is the library list that must be loaded
            URL[] urls = resolveLib(agentDirectory);
            final ClassLoader agentClassLoader = createClassLoader("pinpoint.agent", urls, parentClassLoader, properties);
            final ModuleBootLoader moduleBootLoader = loadModuleBootLoader(instrumentation, parentClassLoader);
            if (moduleBootLoader != null) {
                this.logger.info("defineAgentModule");
                moduleBootLoader.defineAgentModule(agentClassLoader, urls);
            }

            AgentBootLoader agentBootLoader = new AgentBootLoader(agentType.getClassName(), agentClassLoader);
            logger.info(String.format("pinpoint agent [%s] starting...", agentType));

            final List<Path> pluginJars = agentDirectory.getPlugins();
            AgentOption option = createAgentOption(
                    instrumentation,

View on GitHub (pinned to 744c3d3075)

Solutions

Set pinpoint.disable=false in pinpoint.config (or remove the line) and restart the JVM
Verify you are editing the pinpoint.config actually loaded by the agent (log shows the config path)
If disabling is intentional, remove the -javaagent flag instead to avoid partial startup

Example fix

// pinpoint.config
// before
pinpoint.disable=true
// after
pinpoint.disable=false

Defensive patterns

Strategy: validation

Validate before calling

// shell: before launch
grep -E '^\s*pinpoint.disable\s*=\s*true' "$AGENT_DIR/pinpoint.config" && echo "pinpoint disabled in pinpoint.config"

Prevention

Audit pinpoint.config per environment in CI
Set pinpoint.disable=false explicitly rather than relying on defaults
Confirm the loaded config path from agent startup logs before editing

When it happens

Trigger: pinpoint.config in the agent directory contains pinpoint.disable=true while the agent is otherwise attached and enabled at the bootstrap level.

Common situations: Shipped default config with disable=true copied unchanged into production; config templating flipping the flag; leftover setting from a troubleshooting session.

Related errors

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