Let's focus only on the interesting bits of the stack waiting to consume the message: "Monitor Ctrl-Break" #12 daemon prio=5 os_prio=31 cpu=17.42ms elapsed=11.42s tid=0x00007fd7a6896200 nid=0圆603 runnable Īt .SocketDispatcher.read0( /Native Method)Īt .SocketDispatcher.read( /SocketDispatcher.java:47)Īt .yRead( /NioSocketImpl.java:261)Īt .NioSocketImpl.implRead( /NioSocketImpl.java:312)Īt .NioSocketImpl.read( /NioSocketImpl.java:350)Īt .NioSocketImpl$1.read( /NioSocketImpl.java:803)Īt $SocketInputStream.read( /Socket.java:981)Īt .StreamDecoder.readBytes( /StreamDecoder.java:297)Īt .StreamDecoder.implRead( /StreamDecoder.java:339)Īt .StreamDecoder.read( /StreamDecoder.java:188)Īt java.io.InputStreamReader.read( /InputStreamReader.java:181)Īt java.io.BufferedReader.fill( /BufferedReader.java:161)Īt java.io.BufferedReader.readLine( /BufferedReader.java:326)Īt java.io.BufferedReader.readLine( /BufferedReader.java:392)Īt .2$1.run(AppMainV2.java:61) We can see from top to bottom what the different threads are doing at the time of the snapshot. Stack trace: the most important source of information to decipher what is happening with our application.Native ID (nid): the unique ID given by the OS, useful to extract correlation with CPU or memory processing.Java ID (tid): the unique ID given by the JVM.Priority (prior): the priority of the thread.Name: it can provide useful information if developers include a meaningful thread name.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |