Hello! The only thing that stands off is that you have very deep object nesting, of level 12.
Maybe it causes some very rare issue, I recommend trying to see if you will have this problem with flatter objects. This is a long shot, since we have not seen crashes like this one. Regards, -- Ilya Kasnacheev ср, 29 янв. 2020 г. в 13:00, tarunk <[email protected]>: > Hi All, > > We are seeing JVM on an ignite node, the error trace taking us to > > org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write0 > > Below is full stacktrace of error. > We are running ignite 2.7.0 with openjdk 1.8 on RHEL machines. > Can someone please check and suggest what could be the underlying cause ? > Is there any Unsafe/Native API access with this api which might lead to > crash or any bug with this version ? > Attaching the error log file also for more details. > hs_err_pid40132.log > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2364/hs_err_pid40132.log> > > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f47f27d563a, pid=40132, > tid=0x00007f4716cac700 > # > # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build > 1.8.0_222-b10) > # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 > compressed oops) > # Problematic frame: > # J 58563 C2 > > org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write0(Ljava/lang/Object;Lorg/apache/ignite/internal/binary/BinaryWriterExImpl;)V > (761 bytes) @ 0x00007f47f27d563a [0x00007f47f27d5500+0x13a] > # > # Failed to write core dump. Core dumps have been disabled. To enable core > dumping, try "ulimit -c unlimited" before starting Java again > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # > > Thanks > Tarun > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
