-
Notifications
You must be signed in to change notification settings - Fork 278
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
Error after upgrade to 108.1 #3805
Comments
Hi @jendib , thank you for reporting this. Which version of the Datadog agent are you running on the other side? |
Thanks for your quick answer. My agent is running |
It would be great if you could try with and upgraded agent and report back. |
I still have the same issue after upgrading to the latest agent |
Thanks for trying this out. One thing to try would be to enable a newer version of the Java Tracer to Datadog Agent protocol by setting the environment variable |
The agent is running in Kubernetes with the official Helm chart. I was using I added |
@jendib Thanks for confirming that the |
Oops I spoke too soon, the errors came back after a few minutes. |
Hi @jendib I'm sorry to hear that. We are trying to figure out what might be causing this issue. |
Ditto, with https://github.com/DataDog/dd-trace-java/releases/download/v1.2.0/dd-java-agent-1.2.0.jar in our docker image and running From the message, it sounds like no error logs at all (even ones unrelated to this bytes reading problem) would be created - is that true? |
Is there any news or updates you can share regarding the status of this issue? |
We're also getting a similar message:
What could cause the |
Hi! We are experiencing this issue with a Kotlin application. Any tips on how to troubleshoot this issue? dd-trace-java version: |
Same issue with dd-java-agent: The java agent logs: On the datadog agent side we get this error message: There is an open issue for datadog agent for this error message, but also not much information from there: DataDog/datadog-agent#9555 |
I upgraded from an old version to the latest 108.1 and I'm getting these warning every few minutes:
The text was updated successfully, but these errors were encountered: