Dmitrii, What version of Ignite you are using?
I've rechecked Java thin client recently (forgot to share results here), in my tests: Client Version 2.7.0 OracleJDK 11: Client won't start unless "--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED" option is specified. OpenJDK 12: Client can't start at all Client Version 2.7.5 OracleJDK 11: Client starts without any additional options OpenJDK 12: Client starts without any additional options "--add-opens=java.base/java.nio=ALL-UNNAMED" suppress warning messages on all versions. вт, 3 сент. 2019 г. в 16:35, Dmitrii Sherstobitov <dnsherstobi...@gmail.com >: > Hi! > > I've made some simple tests using Apache Ignite documentation for JDBC and > Java Thin client with using of following API functions: > > JDBC: executeQuery, execute, preparedStatement > Java Thin: cache get, put, create > > None of these API requires additional options for JVM. However, some > options are optional and used to suppress warning messages. > > Tested with Open JDK 9.0.4, 10.0.2, 11.0.2, 12.0.2 on Ubuntu and Mac OS. > > > Best regards, Dmitry Sherstobitov > On 26 Aug 2019, 16:22 +0300, Alex Plehanov <plehanov.a...@gmail.com>, > wrote: > > > > Dmitry, > > > > As I said before, thin client uses BinaryHeapOutputStream, which uses > > Unsafe, so "--illegal-access=deny" has an effect. > > With "--illegal-access=deny" thin client will not start unless you > specify > > "--add-opens=java.base/java.nio=ALL-UNNAMED" >
