You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The APM agent version 1.33.0 fails to start on JDK 20, which prevents
the APM integration to work as expected. As a consequence, the
tracing does not work.
When setting `ELASTIC_APM_LOG_LEVEL=debug` and
`ELASTIC_APM_LOG_FILE=/tmp/log.txt`, the agent log shows that there
is an issue with accessing `Unsafe` (sorry I don't have the exact
stack trace).
There was a few changes in APM agent regarding the security manager
(SM) in recent versions, and updating the agent seems to make it
work as expected.
However, there is one known caveat so far
(elastic/apm-agent-java#3074), keeping
the agent with `debug` log level with `ELASTIC_APM_LOG_LEVEL=debug`
makes it trigger another security exception when trying to establish
connection with apm-server because the agent prints few details if
a proxy is used or not (which is forbidden by default by the SM and
isn't yet wrapped in a privileged call.
Backport of: #94716
Co-authored-by: SylvainJuge <[email protected]>
0 commit comments