Eric,
Glad it helped!
And no, I guess that won’t be unique only for your environment.
Thanks for sharing your successful run configuration — hope it helps other
users adopt Ignite to theirs environment as mush as it possible for now.
Also, if possible, please, share with us the results of web
Petr,
Thanks for tip. This is looking very promising as I see Ignite starting in
the catalina.out file now. As a note, I added those directives to my
bin/setenv.sh script as JAVA_OPTS as opposed to JVM_OPTS as that didn't
seem to work. Also, I did have to add the cache-api-1.1.0.jar file to my
Hi, Eric.
Try to add to Tomcat’s JVM_OPTS following directives, please:
--add-exports java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports java.base/sun.nio.ch=ALL-UNNAMED
--add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
--add-exports
Hello,
>From the suggestion on my other thread to try a newer Tomcat, I decided to
spin up Tomcat 8.5.29 with Oracle JDK 9.0.4. I'm attempting to use web
session clustering based on the following pages [1] and [2] as I saw the
2.4.0 release notes say Java 9 is now supported. I copied the
