Does the Java garbage collector stop POSIX threads created from JNI calls?

I have a time critical application that needs to send UDP datagrams according to the set schedule The jitter tolerance of the receiver is very low It is not enough to implement it using java scheduledthreadpoolexecutor, because when the GC executes the "stop the world" collection, my thread will pause when the GC completes its work

I want to implement the business logic in Java and the time critical part in C with POSIX threads (by the way, the native environment is Linux) This will allow us to save thousands of lines of code written in Java and get the required pacing from native system calls

My question is: if I call a JNI function that creates a separate POSIX thread, will the thread be "suspended" when the Java GC executes the "stop world" collection? Does the experienced JNI master have any traps that he would like to point out in this way or suggest any other method?

As always, thanks to the awesome stack overflow community!

Solution

It should not block POSIX threads (assuming that GC does not use so much CPU, other system calls will be blocked) I think it will prevent access to POSIX threads from Java applications, but only for a very limited time