-
Notifications
You must be signed in to change notification settings - Fork 848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exchange$ResponseBodySource.read java.lang.IllegalStateException - closed #6916
Comments
I see firebase in the stacktrace that you posted. That seems like it could be relevant. |
Thank you for looking into this issue.
|
Can you at least provide your full list of dependencies w/ versions? Otherwise, we really have nothing to go on. |
I think I might understand what's happening. The stacktrace shows that the exception originates from reading the body bytes here: Lines 160 to 162 in 3a5222f
I found an issue in OkHttp showing a similar error, where a maintainer indicates that it probably originates from unsynchronized concurrent access to a byte buffer. It shouldn't be possible for our exporter code to call Note the calling class is We could catch wrap / catch the exception here, but I suspect this is a problem with the instrumentation. |
|
It looks like this is running on Android, then, not on Ubuntu as you originally posted, @happysiddharth ? |
Ah, you’re absolutely right—by mistake, I posted that it was running on Ubuntu. This is actually running on Android OS. Pardon me for the mix-up. |
did you see @jack-berg's reply? We both suspect that this is firebase interfering with okhttp instrumentation (or vice-versa), and not something related to the SDK itself. @breedx-splk I don't know if you have any Android specific ideas about what might be happening here? @happysiddharth are you using otel's android instrumentation, or rolling your own? |
Yes we are using otel's android instrumentation |
I'm cool with us transferring this to the android repo then... A couple of follow-ups:
Thanks. |
Also see my response here to a similar issue. To summarize, I don't think the presence of a stacktrace like this in logs alone is enough to indicate something is wrong. As I show in that comment, it could just represent a signal that an export failed, which is a routine part of dealing with unreliable networks like the internet. |
Describe the bug
A clear and concise description of what the bug is.
Steps to Reproduce
Initialize the app and configure OpenTelemetry with an OkHttp-based HTTP exporter.
Trigger an HTTP export process (e.g., by sending telemetry data).
Observe the application crash.
What Did You Expect to See?
The application should process the HTTP response body successfully without throwing exceptions or crashing.
What Did You See Instead?
The application crashes with the exception mentioned above.
What Version and What Artifacts Are You Using?
Artifacts:
opentelemetry-api
opentelemetry-sdk
opentelemetry-exporter-http (OkHttp-based HTTP exporter)
Version: 1.43.0
Environment
Compiler: Java
OS (build): Ubuntu 20.04
Runtime: OpenJDK 11
OS (runtime): Ubuntu 20.04
The text was updated successfully, but these errors were encountered: