Hi Thanks for looking into this.
> First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - > maybe > this is because I have later snapshot of Apache Ignite compiled. The version is already 1.4.195. Second, I had to activate the cluster! You have to activate persistent > cluster after you bring all nodes up. Just add ignite.active(true); on > IgniteConfig.java:92 After, I added "ignite.active(true)" it is working for me. Although, when I remove this line on second run of the app, the original problem persists. Shouldn't the cluster be automatically activated in the second run as said in the documentation? On Fri, Sep 28, 2018 at 6:55 PM ilya.kasnacheev <[email protected]> wrote: > Hello! > > Seems to be working for me after two changes. > > First, I had to change h2 version dependency from 1.4.197 to 1.4.195 - > maybe > this is because I have later snapshot of Apache Ignite compiled. > > Second, I had to activate the cluster! You have to activate persistent > cluster after you bring all nodes up. Just add ignite.active(true); on > IgniteConfig.java:92 > > The error message about activation requirement was clear and I still could > exist app with Ctrl-C. Maybe you have extra problems if you are on some > unstable commit of master branch. > > Regards, > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
