How can I solve "WARNING:An illegal reflective access operation has occurred"

[Paul Arsenio Blanco Reyes]

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/opt/primekey/wildfly-22.0.1.Final/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-14.0.1.Final.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS()
WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

[Darran Lofthouse]

You can safely ignore that one, we will be addressing in a later release.

[Michael Douglass]

It's a warning and reminder to developers to deal with someething which will be a problem in the future:

I guess there are things you can do

https://linuxpip.org/an-illegal-reflective-access-operation-has-occurred/

The "an illegal reflective access operation has occurred" is merely a warning message and only indicating there is reflective access to JDK internal class without doing anything about it. In the meantime, you can either

• You can specify the reflective access explicitly using java's --add-opens parameter. The migration guide for JDK 11 provides more information.
• Use a compatible and certified version of your software. If the software is actively maintained, then the developers are now aware of the warning and a fix may come in the near future.

WARNING: All illegal access operations will be denied in a future release --
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/fb2d883c-dda3-4b92-a197-d84372131c7en%40googlegroups.com.

[Szymon Klepacz]

Issue was reported to version 21, in 26 it's still present.