pinpoint-apm/pinpoint · info
PinPoint is disabled via Env/Property.
Error message
PinPoint is disabled via Env/Property.
What it means
Pinpoint's bootstrap premain logs this warning and exits when the agent is explicitly disabled via the PINPOINT_DISABLE environment variable or the pinpoint.disable system property. It is an intentional shutdown, not a fault.
Source
Thrown at agent-module/bootstraps/bootstrap/src/main/java/com/navercorp/pinpoint/bootstrap/PinpointBootStrap.java:50
import java.util.Map;
import java.util.Objects;
import java.util.jar.JarFile;
/**
* @author emeroad
* @author netspider
*/
public class PinpointBootStrap {
private static final BootLogger logger = BootLogger.getLogger(PinpointBootStrap.class);
private static final LoadState STATE = new LoadState();
public static void premain(String agentArgs, Instrumentation instrumentation) {
if (DisableOptions.isBootDisabled()) {
if (logger.isWarnEnabled()) {
logger.warn("PinPoint is disabled via Env/Property.");
}
return;
}
final boolean success = STATE.start();
if (!success) {
logger.warn("pinpoint-bootstrap already started. skipping agent loading.");
return;
}
PinpointBootStrap bootStrap = new PinpointBootStrap(agentArgs, instrumentation);
bootStrap.start();
}
private final String agentArgs;
private final Instrumentation instrumentation;
View on GitHub (pinned to 744c3d3075)
Solutions
- Remove the disable flag (env PINPOINT_DISABLE or -Dpinpoint.disable=true) if the agent should run
- If disabling is intentional, also remove -javaagent:pinpoint-bootstrap.jar from the JVM args to silence the warning
- Confirm the exact DisableOptions key in use (boot env vs config property) matches what your launch script sets
Example fix
// before java -javaagent:pinpoint-bootstrap.jar -Dpinpoint.disable=true -jar app.jar // after java -javaagent:pinpoint-bootstrap.jar -jar app.jar
Defensive patterns
Strategy: validation
Validate before calling
// shell: before launching if [ -n "$PINPOINT_DISABLE" ] || echo "$JAVA_OPTS" | grep -q 'pinpoint.disable=true'; then echo "pinpoint disabled: remove -javaagent flag" fi
Prevention
- Keep disable flags and -javaagent flags in sync in launch templates
- Use one source of truth for agent enablement per environment
- Log effective JVM args at startup for auditability
When it happens
Trigger: JVM launched with -Dpinpoint.disable=true (or DisableOptions BOOT env var set) while -javaagent:pinpoint-bootstrap.jar is still on the command line.
Common situations: Deliberately disabling Pinpoint in dev/CI while forgetting to remove the -javaagent flag; templated launch scripts toggling the disable flag; copying a JVM command line between environments.
Related errors
- value of disable property is not false, pinpoint.disable=tru
- Unknown AgentType:
- Failed to detect pinpoint profile. Please add -Dpinpoint.act
- unsupported profile or profile alias:
- %s load fail Caused by:%s
AI-assisted analysis of pinpoint-apm/pinpoint@744c3d3075 (2026-09-07).
Data as JSON: /api/errors/ab35c10dc8720733.
Report an issue: GitHub.