[Bug]: OTel API version mismatch lets NoSuchMethodError escape PluginRunner
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- aws, java
- Ambito
- backend, observability, testing
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Resolve
software.amazon.lambda.durable:aws-durable-execution-sdk-java-plugin-otel:2.2.1and its dependencies. - Compile
B1Probebelow 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. - Run with the normal dependencies (OTel API/context 1.66.0 in the tested resolution). Observe
result=returned. - Resolve
io.opentelemetry:opentelemetry-api:1.49.0andio.opentelemetry:opentelemetry-context:1.49.0, place those two jars before the normal dependency classpath, and run the same compiled class. Observeresult=escaped_plugin_runnerand 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.
- Lingua principale
- Java
- Stelle
- 28
- Fork
- 13
- Merge medio
- 2g 8h
- PR unite (30g)
- 40
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aws/aws-durable-execution-sdk-java
-
bug pkg:sdk
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
aws/aws-durable-execution-sdk-java#773 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation pkg:sdk
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
aws/aws-durable-execution-sdk-java#645 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
aws/aws-durable-execution-sdk-java#300 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: root handler instrumentation misses the canonical OTel execution contextForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertaneeds-triage
Difficoltà 5/5 Più di una settimana Idoneità per principianti 40/100
aws/aws-durable-execution-sdk-java#770 ·
I maintainer di solito rispondono entro 1 giorno
-
[Feature]: Propagate per-operation trace context for chained invokesForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertaenhancement needs-triage
Difficoltà 5/5 Più di una settimana Idoneità per principianti 38/100
aws/aws-durable-execution-sdk-java#764 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di aws/aws-durable-execution-sdk-java
Issue simili
-
component/operate kind/feature-request
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Forge coverage prompts carry text the agent cannot act onForse già presa @graalvmbot l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
oracle/graalvm-reachability-metadata#10572 ·
I maintainer di solito rispondono entro 1 giorno
-
[CI] Core CI doesn't run for changes to amoro-format-lance (and amoro-web)Forse già presa @MarkAlex1234 l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
area/docs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno