Closed tbradellis closed 1 year ago
Jira CommentId: 210443 Commented by csanchezfabres:
Scala; [1000 accounts|https://onenr.io/0KQXpP8E0Qa] , and only [261 |https://docs.google.com/spreadsheets/d/17JbsubO5x5MGXNQaY9vzVrMFyKneJMlAXAXxipETX7g/edit#gid=0]are using scala 2.13 and java 11+
Potentially, upgrading to Java 17 solves this problem
Jira CommentId: 210443 Commented by csanchezfabres:
Scala; [1000 accounts|https://onenr.io/0KQXpP8E0Qa] , and only [261 |https://docs.google.com/spreadsheets/d/17JbsubO5x5MGXNQaY9vzVrMFyKneJMlAXAXxipETX7g/edit#gid=0]are using scala 2.13 and java 11+
Potentially, upgrading to Java 17 solves this problem (to be confirmed). Decision pending unless there's clarity on path forward
Jira CommentId: 213835 Commented by bellis:
Can confirm that we still see this exception on Java 17 and 20.
Will not be able to take this up in the coming Jul-Sep quarter; will consider this issue for the following quarter.
Description
The agent throws exceptions when running on Java 11+ and Scala 2.13x.
Some customers report interference with reporting Transactions and custom attributes.
From local reproduction test:
Expected Behavior
No exceptions thrown and agent otherwise reports all expected transactions and attributes.
Steps to Reproduce
This can be reproduced: Quick and easy: pull this app down and setup to run with the agent as described in the readme. https://github.com/newrelic/newrelic-java-examples/tree/main/newrelic-java-agent/scala/segment-api-synchronous Update sbt build and .jvmoptions to the versions given below. Run the app.
This app uses the scala api (which essentially just calls the java agent api). However, you can change the example app to use the direct Java API calls like so:
(then update the libraryDependencies to accomodate)
Your Environment
Java 11 zulu hotspot. Scala 2.13.10.