Dear JDK developers,

I'd like to propose adding an option that allows the JVM to ignore a
non-existent -javaagent instead of aborting.

Currently, if a -javaagent is specified but the agent jar file doesn't
exist, the JVM aborts with an error. This can cause issues in environments
where the same JVM arguments are used across different systems, but not all
systems have the agent installed.

The proposed option (e.g. -XX:+IgnoreNonExistentJavaAgent) would allow the
JVM to continue starting up even if the specified agent jar is not found,
simply skipping that agent.

This could improve flexibility and ease deployment in heterogeneous
environments.

Potential considerations:
1. Security implications of silently ignoring a missing agent
2. Logging when an agent is skipped
3. Interaction with other agent-related options

I'd appreciate your thoughts on this proposal. Is this something that would
be valuable to the community? Are there any concerns or alternative
approaches we should consider?

Thank you for your time and consideration.

Thiago

Reply via email to