-
Notifications
You must be signed in to change notification settings - Fork 573
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
Illegal reflective access #321
Comments
It seems that there are also issues with OpenJ9 in the same area (in this case I tested with the Java 8 flavor in the context of R3 Corda):
|
to reproduce one can attempt to build https://github.com/corda/cordapp-example with https://adoptopenjdk.net/releases.html?variant=openjdk8&jvmVariant=openj9 (64-bit, jdk, java 8) |
I'm not sure if that's related to this issue or not. |
yes, not the exactly same issue: ones a different kind of jdk, the other time restrictions of newer jdks. But in both cases caused by ThreadAccess doing rather JDK-implementation-specific reflection access. |
I believe this warning is a result of the new Java module system. To get rid of this warning add: |
While it may still work when --illegal-access gets changed to deny, future versions of Java will explicitly remove illegal reflective access altogether and it is quite likely this library will no longer work unless the code in question is explicitly changed. In other words, |
I agree that the code should be changed, if possible, but I also thought that the "--add-opens" approach provided a permanent solution, since it is part of the module management system. If that is not the case, I'd like to learn about it and would greatly appreciate it if you could point me in the right direction. |
The OpenJ9 issue arises from the fact that there is no 'target' variable in the thread class. This is arguably a private field. I suspect it is actually a separate issue though. I believe it is worthy of remediation |
I experience same problem in openJ9 my microservie does not loads any WA for this ? |
Hello,
In newer versions of Java beyond 11, illegal reflective access will be denied by default and eventually it will no longer be allowed at all. Currently, Quasar throws an illegal reflective access warning as follows:
Is there anything that can be done to fix this? I know that for example, netty has fixed their illegal reflective access: netty/netty#8318 and pgjdbc has fixed their illegal reflective access as well: bolcom/pgjdbc@5865257
I think fixing this is important to ensure that Quasar will continue working in Java versions beyond 11. I did not see any other issues mentioning this so I decided to open my own issue for this.
Thank you.
The text was updated successfully, but these errors were encountered: