Skip to content
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

jfr-connection: wrong parameter sent to JFR DiagnosticCommand #1491

Closed
dsgrieve opened this issue Oct 10, 2024 · 1 comment
Closed

jfr-connection: wrong parameter sent to JFR DiagnosticCommand #1491

dsgrieve opened this issue Oct 10, 2024 · 1 comment

Comments

@dsgrieve
Copy link
Contributor

Component(s)

No response

What happened?

Description

The DiagnosticCommands for JFR have a "name" and a "recording" parameter. The "recording" parameter is the id of the recording, which is what should be used in those commands where a recording or name are needed. The code currently uses "name" which works for most JVMs (if the name is not set then name is the recording id), but not all.
Observed on

java version "1.8.0_401"
Java(TM) SE Runtime Environment (build 1.8.0_401-b10)
Java HotSpot(TM) 64-Bit Server VM (build 25.401-b10, mixed mode)

Trying to dump a recording failed to produce a file, but did not produce any exceptions.

Steps to Reproduce

Expected Result

Actual Result

Component version

1.38.0

Log output

No response

Additional context

Observed with Microsoft's Application Insights 3.6.0

dsgrieve added a commit to dsgrieve/opentelemetry-java-contrib that referenced this issue Oct 10, 2024
@laurit
Copy link
Contributor

laurit commented Oct 18, 2024

Resolved with #1492

@laurit laurit closed this as completed Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants