WARNING: Illegal reflective access by org.hsqldb.persist.RAFileNIO (file:/home/aaime/.m2/repository/org/hsqldb/hsqldb/2.4.1/hsqldb-2.4.1.jar) to method java.nio.DirectByteBuffer.cleaner()
I can confirm this issue. I use the epsg database and get the following warning (using java 9 and hsqldb 2.4.1):
...
INFORMATION: dataFileCache commit end
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.hsqldb.persist.RAFileNIO (file:/D:/lib/hsqldb.jar) to method java.nio.DirectByteBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of org.hsqldb.persist.RAFileNIO
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
...
regards
Micha
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am also observing this warning, using HSQLDB 2.4.1 in a web application deployed on Apache Tomcat running with OpenJDK 11.0.2.
There is a workaround.
If I add the following option to Java command line, the warning disappears:
--add-opens=java.base/java.nio=ALL-UNNAMED
For sake of completeness, I should add that
startup scripts of Apache Tomcat also add the following options to the command line. I do not know whether they are important for HSQLDB. (Source code)
Hello,
I can confirm this issue. I use the epsg database and get the following warning (using java 9 and hsqldb 2.4.1):
... INFORMATION: dataFileCache commit end WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.hsqldb.persist.RAFileNIO (file:/D:/lib/hsqldb.jar) to method java.nio.DirectByteBuffer.cleaner() WARNING: Please consider reporting this to the maintainers of org.hsqldb.persist.RAFileNIO 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 ...
regards
Micha
I am also observing this warning, using HSQLDB 2.4.1 in a web application deployed on Apache Tomcat running with OpenJDK 11.0.2.
There is a workaround.
If I add the following option to Java command line, the warning disappears:
For sake of completeness, I should add that
startup scripts of Apache Tomcat also add the following options to the command line. I do not know whether they are important for HSQLDB. (Source code)
Fixed and committed for version 2.5.0
Fixed and committed for version 2.5.0
Thank you for your effort.