-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Avoid illegal reflective access in ContextOverridingClassLoader.isEligibleForOverriding #22791
Comments
I'm not sure there is much we can about this one since there is no public replacement API for it... Load-time weaving is generally a quite involved affair, we're not aiming for a warning-free experience on JDK 9+ there quite yet. |
Got it, just wanted to make sure it's a known issue. |
5.2.2 is also affected using OpenJDK 11 - I have a different trace using the spring instrumentation agent and aspectj load time weaving:
|
As of Java 16 this is not a warning anymore and it prevents starting the application. Knowing that Java 17 is the next LTS, people will start moving to that version, most likely hitting this issue. |
I'm using java 16 and the app failed to start when I tried to use load time weaving and shedlock together, I have added the java option --add-opens java.base/java.lang=ALL-UNNAMED but it still doesn't work, for details please see lukas-krecan/ShedLock#853. |
The workaround of adding |
any update on this ? We are in the process of upgrading our application to spring/spring boot(v3), we are using class instrumentation and just wondering if there are any plans to get rid of this reflection call, so we can simplify startup and get rid of --add-opens=java.base/java.lang=ALL-UNNAMED as some security scans alerts about that.... |
Since there is no replacement API for finding pre-loaded classes, we can only really ignore that case if the With that change applied, |
Affects: 5.1.6
Or in test:
The text was updated successfully, but these errors were encountered: