-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Add jdk.management.agent module to server boot layer on start #123938
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
Add jdk.management.agent module to server boot layer on start #123938
Conversation
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| .findModule(module.getName()) | ||
| .map(ResolvedModule::reference) | ||
| .orElse(null); | ||
| return module == PolicyManager.class.getModule() || (moduleReference != null && systemModules.contains(moduleReference)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's the entitlements module we could return earlier? Then we don't need to do the reference unwrapping.
|
@rjernst as discussed I've modified this to simply add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Some system modules are not initially loaded by the boot module layer. An example is something like
jdk.management.agentwhich dynamically loaded by various external tools, such as IDEs when performing thread or heap dumps.We now proactively add this module via
--add-modulesto the server so it's known to thePolicyManageron startup.