Not that it excuses the crash, but why are you calling activate every time the node starts? It should be called once, the first time all the nodes are present. The cluster will auto-activate every time after that.
Regards, Stephen > On 7 Jan 2021, at 08:56, rakshita04 <[email protected]> wrote: > > it works, the process is stopped but when application is started using the > same Database node, it crashes with below logs on terminal- > Ignite node stopped OK [uptime=00:00:55.197] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x76c9f208, pid=26716, tid=26716 > # > # JRE version: OpenJDK Runtime Environment (11.0.6+10) (build > 11.0.6+10-post-Debian-1deb10u1) > # Java VM: OpenJDK Server VM (11.0.6+10-post-Debian-1deb10u1, mixed mode, g1 > gc, linux-) > # Problematic frame: > # C [libignite-2.8.0.44294.so.0+0x11208] > ignite::Ignite::SetActive(bool)+0xb > > Our application is calling SetActive method after node::start(). > > The application is recovered only when Databse is deleted and node is > started again. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
