Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug]: OTel API version mismatch lets NoSuchMethodError escape PluginRunner

Cerrado
  • ¿Algo no está bien?
#763 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #780 de @zhongkechen — fusionado

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, java
Área
backend, observability, testing

Línea de trabajo

Start with otel-plugin/src/main/java/software/amazon/lambda/durable/otel/OtelPluginSupport.java and sdk/src/main/java/software/amazon/lambda/durable/plugin/PluginRunner.java, then run the supplied B1Probe with OTel API/context 1.66.0 and 1.49.0. Done means the older-API case is safely diagnosed or contained, compatible tracing still works, regression and control coverage exist, and plugin failure does not block healthy plugins or the handler.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug needs-triage
Expected Behavior

An incompatible OpenTelemetry agent/API combination should produce a clear compatibility diagnostic or disable the affected instrumentation without a nonfatal linkage error escaping the plugin boundary and failing the customer invocation. Compatible configurations should continue to trace normally; fatal JVM failures need their existing separate handling.

Actual Behavior

The global-provider path calls GlobalOpenTelemetry.isSet(). If an older OpenTelemetry API is the class visible to the plugin, that method is unavailable and throws NoSuchMethodError. The published PluginRunner catches Exception, so this Error escapes.

Using the real plugin and runner, OTel API 1.66.0 returned normally; API 1.49.0 placed first on the classpath produced java.lang.NoSuchMethodError: boolean io.opentelemetry.api.GlobalOpenTelemetry.isSet() outside PluginRunner.onInvocationStart. The older API models agent/classloader version skew; this probe did not deploy an actual Java agent.

Steps to Reproduce
  1. Resolve software.amazon.lambda.durable:aws-durable-execution-sdk-java-plugin-otel:2.2.1 and its dependencies.
  2. Compile B1Probe below in the indicated package. The package placement permits the test to mark the agent auto-configuration path as installed; this is a reproduction fixture, not recommended application code.
  3. Run with the normal dependencies (OTel API/context 1.66.0 in the tested resolution). Observe result=returned.
  4. Resolve io.opentelemetry:opentelemetry-api:1.49.0 and io.opentelemetry:opentelemetry-context:1.49.0, place those two jars before the normal dependency classpath, and run the same compiled class. Observe result=escaped_plugin_runner and NoSuchMethodError. No AWS calls are made.
Reproduction code 
package software.amazon.lambda.durable.otel;
import java.time.Instant;
import java.util.List;
import io.opentelemetry.api.GlobalOpenTelemetry;
import software.amazon.lambda.durable.plugin.InvocationInfo;
import software.amazon.lambda.durable.plugin.PluginRunner;
public class B1Probe {
 public static void main(String[] args) {
  OtelPluginAutoConfigurationState.markInstalled();
  var plugin = new ExecutionOtelPlugin(OtelPluginConfig.builder().enableMdc(false).build());
  var runner = new PluginRunner(List.of(plugin));
  boolean hasMethod = java.util.Arrays.stream(GlobalOpenTelemetry.class.getMethods()).anyMatch(m -> m.getName().equals("isSet"));
  try {
   runner.onInvocationStart(new InvocationInfo("req", "arn:aws:lambda:us-west-2:123456789012:function:probe:1/durable-execution/probe/id",true,Instant.now()));
   System.out.println("{\"apiHasIsSet\":"+hasMethod+",\"result\":\"returned\"}");
  } catch (Throwable e) {
   System.out.println("{\"apiHasIsSet\":"+hasMethod+",\"result\":\"escaped_plugin_runner\",\"errorType\":\""+e.getClass().getName()+"\",\"error\":\""+e.getMessage().replace("\"","\\\"")+"\"}");
  }
 }
}
SDK Version

Core SDK / OTel plugin 2.2.1; OTel API/context 1.66.0 control and 1.49.0 mismatch. Main rechecked at 78574e3051aac9b5ca00a0c1fd2b91eab72a9e15.

Java Version

Corretto 25.0.4.1

Is this a regression?

Unknown; no last-known-good version has been established.

Additional Context

Sources: global provider compatibility path and Exception-only plugin dispatch catch. This does not assert that every older agent version must be supported; it requests safe handling of an incompatible visible API.

The open PR #721 includes plugin lifecycle/error-isolation work and is relevant to the containment part. This issue tracks the concrete API-skew regression and supported-configuration behavior.

Acceptance criteria
  • Guard/remove calls to APIs that may be absent, or safely detect and explain the required API/agent version before calling them.
  • Contain nonfatal linkage failures from plugin hooks/factories without blanket-catching fatal JVM errors.
  • Add the older-API regression and compatible-version control, then test the supported real agent combinations.
  • Document version requirements and ensure a failed plugin does not prevent healthy plugins or the handler from completing.
Lenguaje dominante
Java
Estrellas
28
Forks
14
Merge medio
2 d 19 h
PR fusionados (30 d)
43

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aws/aws-durable-execution-sdk-java

Todos los issues de aws/aws-durable-execution-sdk-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.