ReflectUtils | Java reflect tool | Reflection library

Since JDK 16, the default for the --illegal-access option is deny, so “deep reflection” to JDK classes fails.

You can override the behavior by specifying --illegal-access=permit, but you have to be aware of JEP 403: Strongly Encapsulate JDK Internals which is about closing that possibility in a future version, so this option is only a temporary solution.

The permanent solution is to update cglib to a compatible version if/once it exists. The attempt to access ClassLoader.defineClass suggests that the library wants to add classes to a particular context, which can be done via MethodHandles.lookup().defineClass instead (since Java 9). So the code only has to switch to the new way of adding classes.

You’re using an old version of spring-data-aerospike (2.0.1.RELEASE was released on April 2019) is there any chance you can upgrade to the latest version? 2.4.2.RELEASE

You can see how to setup a simple spring data aerospike application here: https://medium.com/aerospike-developer-blog/simple-web-application-using-java-spring-boot-aerospike-database-and-docker-ad13795e0089

Please share the entire project’s code and the entire exception.

I would look into:

1. The configuration class (The Aerospike Beans creation).
2. The content of the testEntity class - are you using @Id annotation on the primary key field?
3. Extending the repository class with specifying the testEntity object (… extends AerospikeRepository {) you can see an example in the link I added.

As it turned out all I had to do was add the Signature package nl.omgwtfbbq.delver to jboss system modules so it can be visible to all applications

The issue cause is found after doing some more digging.

Issue cause: The default quality profile corresponding to the C++ (Community) had their all rules disabled by default, and there was no option to enable them as well.

Fix: Created a new quality profile extending the default one, then enabled rules for that, and finally made it as the default quality profile for C++ (Community) solves the issue.

Update (16-Feb-'21): Got a clarification from sonar-cxx team that this is intentional as well, and the same is documented in https://github.com/SonarOpenCommunity/sonar-cxx/wiki/Manage-Quality-Profiles

Since the cxx plugin contains a large number of sensors with over 4000 rules, all rules are initially deactivated in the default profile Sonar way for the programming language CXX. Enabling all rules would have a negative impact on the analysis performance and mostly only a subset is needed.

Therefore, after installation, no sensor issues are displayed. To display issues, the corresponding rules must first be enabled in the Quality Profile being used by the project.

I found a solution by erasing the local copy of the repository, downloading it again and recompiling everything:

You put the declarations into . To execute them you need to move them to the section.

BTW: You defined the Java version at three locations in the POM which is not really sensible.

Spring Cloud Gateway is built on Project Reactor and already contains a Netty (instead of Tomcat server).

So please try to remove:

Ok, so I found the culprit, turns out it was the Java 9 module-info.java, I encountered an issue making RabbitMq work, all files were imported correctly but it was pointing to say the error was coming from my module-info.java so I removed it, after removing it I have not had this problem (and RabbitMq worked too), from my understanding, their are internal classes that were not put on the allow list that need to access my classes and because of that the app kept failing, the app has been working since then without any problems.

Am not sure, but i think the problem caused by spring-core dependency. Can you try to remove spring-core dependency from pom.xml file and try to run it again.