I have tested solution with java-thread and GC logs had contain same pause values of thread stopping which was detected by java-thread.
My log (contains pauses > 100ms): [2017-11-20 17:33:28,822][WARN ][Thread-1][root] Possible too long STW pause: 507 milliseconds. [2017-11-20 17:33:34,522][WARN ][Thread-1][root] Possible too long STW pause: 5595 milliseconds. [2017-11-20 17:33:37,896][WARN ][Thread-1][root] Possible too long STW pause: 3262 milliseconds. [2017-11-20 17:33:39,714][WARN ][Thread-1][root] Possible too long STW pause: 1737 milliseconds. GC log: gridgain@dell-5580-92zc8h2:~$ cat ./dev/ignite-logs/gc-2017-11-20_17-33-27.log | grep Total 2017-11-20T17:33:27.608+0300: 0,116: Total time for which application threads were stopped: 0,0000845 seconds, Stopping threads took: 0,0000246 seconds 2017-11-20T17:33:27.667+0300: 0,175: Total time for which application threads were stopped: 0,0001072 seconds, Stopping threads took: 0,0000252 seconds 2017-11-20T17:33:28.822+0300: 1,330: Total time for which application threads were stopped: 0,5001082 seconds, Stopping threads took: 0,0000178 seconds // GOT! 2017-11-20T17:33:34.521+0300: 7,030: Total time for which application threads were stopped: 5,5856603 seconds, Stopping threads took: 0,0000229 seconds // GOT! 2017-11-20T17:33:37.896+0300: 10,405: Total time for which application threads were stopped: 3,2595700 seconds, Stopping threads took: 0,0000223 seconds // GOT! 2017-11-20T17:33:39.714+0300: 12,222: Total time for which application threads were stopped: 1,7337123 seconds, Stopping threads took: 0,0000121 seconds // GOT! -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
