CODEWITHSUNDEEP
javajvmfreezearm64g1gc
xijiu
xijiu

Reputation: 1

JVM hang suddenly with jdk version 8u1.8.0_312

Our online Kafka Broker service suddenly hung up, and it's occurs with low probability and without any time regularity. no crash, no warning, no error and no logs

The command "jstack [pid]" no response, then I print the stack trace with command "jstack -m [pid]", and I found all threads state are BLOCKED, include VM Thread.

VM Thread stack:

ox0000ffff99f4da8c __pthread_cond_wait
ox0000ffff997c014c _ZN2os13PlatformEvent4parkEv
ox0000ffff9976f014 _ZN7Monitor5IWaitEP6Thread1
ox0000ffff9976faf0 _ZN7Monitor4waitEblb
ox0000ffff999355dc _ZN20SuspendibleThreadSet11synchronizeEv
ox0000ffff99858a68 _ZN20SafepointSynchronize5beginEv
ox0000ffff999d3124 _ZN8VMThread4loopEv
ox0000ffff999d3458 _ZN8VMThread3runEv
ox0000ffff997b8204 _ZL10java_startP6Thread
ox0000ffff99f47800 start_thread

Only one thead state is IN_NATIVE, it's stack trace:

ox0000ffff99de7dd8 __GI___poll
ox0000fffed7871a3c NET_Timeout0
ox0000fffe786ec40 Java_java_net_PlainSocketImpl_socketAccept
ox0000ffff8c015628 * java.net.PlainSocketImpl.socketAccept(java.net.SocketImpl) bci:0 (Interpreted frame)
ox0000ffff8c008498 * java.net.AbstractPlainSocketImpl.accept(java.net.SocketImpl) bci:7 line:409 (Interpreted frame)
ox0000ffff8c008498 * java.net.ServerSocket.implAccept(java.net.SocketImpl)
ox0000ffff8c008498 * java.net.ServerSocket.accept()
ox0000ffff8c008380 * sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept()
ox0000ffff8c008380 * sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop()

I'm not sure whether this is a JVM bug. Maybe IN_NATIVE thread is useless, STS call synchronize() stuck.

Linux on aarch64, and jdk version is openjdk version "1.8.0_312" OpenJDK Runtime Environment (build 1.8.0_312-b07) OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)

I try to find out the reason, but the JVM hang

Upvotes: -1

Views: 209

Answers (1)

jmc
jmc

Reputation: 1

it is seemed like a JVM bug, if it's a deadlock, the command "jstack [pid]" should be responsed.

Upvotes: 0

Related Questions