pinpoint-apm/pinpoint · warning
Invalid application type configured
Error message
Invalid application type configured : {}, defaulting to {} What it means
WARN in ConfiguredApplicationTypeProvider: the application type resolved from the configured application type name is neither UNDEFINED nor a WAS-type ServiceType, so it is considered invalid and the provider falls back to ServiceType.UNDEFINED. The agent still runs, but the app is not classified as the intended type (e.g. not treated as a WAS node).
Solutions
- Correct the application service type name in pinpoint.config to a known WAS-type ServiceType (or remove it to use the default).
- Check the Pinpoint version's supported ServiceType list for the exact name string.
- Accept the UNDEFINED fallback if a non-WAS type is genuinely intended.
Example fix
// before (pinpoint.config) profiler.application.servicetype=UNKNOWN_TYPE_X // after profiler.application.servicetype=STAND_ALONE
Defensive patterns
Strategy: validation
Validate before calling
ServiceType type = ServiceTypeFactory.of(configuredName);
if (ServiceType.UNDEFINED.equals(type) || !type.isWas()) {
logger.warn("Configured application type '{}' is not a valid WAS type", configuredName);
} Prevention
- Copy service type names exactly from the Pinpoint version's ServiceType list.
- Validate pinpoint.config in CI before deploying agents.
- After upgrading Pinpoint, re-check for renamed service types.
When it happens
Trigger: Setting profiler.application servicetype (or the configured application type) to a name that resolves to a non-WAS or unknown ServiceType; the lookup returns a type that fails applicationType.isWas().
Common situations: Typo in the service type name in pinpoint.config; using a service type valid on the collector but not recognized by the agent; upgrading Pinpoint where a type was renamed.
Understand the failure class
Background: Invalid enum value errors: "Unknown type", "Invalid scope", "must be one of" — when a string is not on the library's allowed list — this error's family across 23 libraries.
Related errors
- - agentId
- - agentName
- application serviceType not found. code:, name:
- - applicationName
- can't find SslProvider. value:+providerType
AI-assisted analysis of pinpoint-apm/pinpoint@744c3d3075 (2026-09-07).
Data as JSON: /api/errors/b2445d7be668bb6e.
Report an issue: GitHub.
Appendix: source
Thrown at agent-module/profiler/src/main/java/com/navercorp/pinpoint/profiler/context/provider/ConfiguredApplicationTypeProvider.java:58
public ConfiguredApplicationTypeProvider(InstrumentConfig instrumentConfig, ServiceTypeRegistryService serviceTypeRegistryService) {
Objects.requireNonNull(instrumentConfig, "instrumentConfig");
this.serviceTypeRegistryService = Objects.requireNonNull(serviceTypeRegistryService, "serviceTypeRegistryService");
this.applicationTypeString = instrumentConfig.getApplicationServerType();
}
@Override
public ServiceType get() {
ServiceType applicationType = serviceTypeRegistryService.findServiceTypeByName(applicationTypeString);
if (applicationType == null) {
return ServiceType.UNDEFINED;
}
if (ServiceType.UNDEFINED.equals(applicationType)) {
return ServiceType.UNDEFINED;
}
if (applicationType.isWas()) {
return applicationType;
}
logger.warn("Invalid application type configured : {}, defaulting to {}", applicationType, ServiceType.UNDEFINED);
return ServiceType.UNDEFINED;
}
}
View on GitHub (pinned to 744c3d3075)