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

[Bug] Better handling missing modules in target JVM #616

Open
grzesuav opened this issue Aug 23, 2024 · 2 comments
Open

[Bug] Better handling missing modules in target JVM #616

grzesuav opened this issue Aug 23, 2024 · 2 comments
Labels
bug Something isn't working needs-triage Needs thorough attention from code reviewers

Comments

@grzesuav
Copy link

Current Behavior

Currently, when jdk.management.jfr module is missing in target VM, :

Expected Behavior

See notification / popup suggesting what is the actual problem, like missing JFR module

Steps To Reproduce

No response

Environment

- OS:
- Environment:
- Version:

Anything else?

Related discussion - #595 (reply in thread)

@grzesuav grzesuav added bug Something isn't working needs-triage Needs thorough attention from code reviewers labels Aug 23, 2024
@andrewazores
Copy link
Member

#595 (reply in thread)

@grzesuav
Copy link
Author

Just to put here idea by @andrewazores : possibly check MXBeans present in target vm.

IIRC there are two versions of connection (because of differences in java versions):

  • V1 - link - ???
  • V2 - link -in this case java.management and java.management.jfr modules are needed, not sure about MXBeans

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Needs thorough attention from code reviewers
Projects
None yet
Development

No branches or pull requests

2 participants