[Native Image] If a Java sub-thread is not closed, the TearDown Isolate process keeps waiting.

[MicroGery]

Describe the Issue

I construct a scenario where Java code takes a child thread from the thread pool to execute a task, but it does not close properly. When I TearDown Isolate, the interface keeps waiting for the thread to close.

Using the latest version of GraalVM can resolve many issues.

• I tried with the latest version of GraalVM.

GraalVM Version

java 17.0.10 2024-01-16 LTS
Java(TM) SE Runtime Environment Oracle GraalVM 17.0.10+11.1 (build 17.0.10+11-LTS-jvmci-23.0-b27)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 17.0.10+11.1 (build 17.0.10+11-LTS-jvmci-23.0-b27, mixed mode, sharing)

Operating System and Version

Red Hat Enterprise Linux Server 7.6 (Maipo)

Troubleshooting Confirmation

• I tried the suggestions in the troubleshooting guide.

Run Command

I dynamically loaded my native_image.so

Expected Behavior

I would like to have an interface to force all Java threads to shut down and return to the C/C++ logic that calls Isolate.

Actual Behavior

I would like to have an interface to force all Java threads to shut down and return to the C/C++ logic that calls Isolate.

Steps to Reproduce

private static final ExecutorService testPool = Executors.newFixedThreadPool(2, r -> new Thread(r, "test_pool_xxx"));
testPool.execute(() -> {
while (true) {
try {
Thread.sleep(1000);
} catch (InterruptedException e) {
System.out.println("test thread interrupted. " + Thread.currentThread().getClass().getName());
break;
}
}
});

Additional Context

No response

Run-Time Log Output and Error Messages

No response

[selhagani]

Hi @MicroGery,

Thank you for reaching out to us!
Could you please try testing using the latest available version of GraalVM here and let me know if you're still experiencing the issue.

[MicroGery]

Member
OK, I'll try to switch to the latest version and rerun my test case.