Hello! We are using Unsafe API in this method, which may lead to JVM crashes not caused by any bugs in JVM.
However, in this case I don't see any other reports about JVM crash in this method. What specific version of Ignite are you using? Have you tried using different HotSpot compiler, such as client vs. server? Have you considered upgrading to Java 11? Regards, -- Ilya Kasnacheev вт, 21 янв. 2020 г. в 08:54, tarunk <tarun.swprofessio...@gmail.com>: > Thanks Ilya, > > The node is not same always where it comes, and it keep changing. > > We got all nodes hardware/OS checked by respective teams, also raised the > case with RedHat and got the response this should be service issue as only > specific service is crashing. > > Curios to know why we got this raised as Compiler type crash as per > > https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/crashes001.html > This seems to be matching 5.1.2 Crash in Compiled Code from above doc as > the > type of problematic frame is "J". > > Thanks > Tarun > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
