process-aot stuck

[8502596]

When I try to run process-aot . It has remained in this state without any errors.

run it whitout AOT,it's ok. Use spring boot 3.4.5 or 3.4.4

[wilkinsona]

Thanks for the report, but you haven't provided enough information to diagnose the problem. If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[8502596]

It's difficult to determine which incompatible component of Spring Boot AOT caused it . My project is throughRuoyi
change spring boot 2.x -> spring boot parent 3.4.4 or 3.4.5 shiro 1.x -> shiro 2.0.4

This project has many extensions 后台扩展

Unfortunately, this project does not have support for Spring Native Image&AOT.In my opinion,The question is whether Spring Boot AOT is stable enough.

For example, if a problem like mine occurs where the process oot is stuck without any errors and does not stop? This should be further explained by the plugin spring boot Maven plugin. Please forgive me for using the idea to click on the plugin's process hot option
In fact, I added the source code of spring boot Maven plugin for debugging, and there were no errors in any of the methods called
And configured
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005

Debugging the code of other modules in Spring Boot: JavaProcessExecutor calls processbuild calls new SpringApplicationAotProcessor(application, settings, applicationArgs).process();
But I found that new SpringApplicationAotProcessor(application, settings, applicationArgs).process();
Unable to end, it is speculated that there are threads waiting for it to run continuously, such as the bean initialization not ending

[8502596]

I suspect it's Shiro's fault because there are some issues with this component, but I think
The Spring Boot Maven plugin must provide more details such as which components need to be initialized and which components have already been initialized
We need to provide more information to identify problematic components. Even if it's a third-party component issue, it should be discovered through the Spring Boot Maven plugin rather than relying solely on the third-party component's logging system to determine if the process oot has completed processing the component

[8502596]

From my perspective
It is not enough to only determine whether the exit is normal, and some information about the Spring loader needs to be obtained at the same time.

This may seem similar to the functionality of an actuator, please forgive me. In fact, I haven't had much experience with actuators and they don't seem to be completely related to process aot. However, using only exitCode to handle details in process-aot seems too simple.

[wilkinsona]

Unfortunately, without a minimal sample, we're not going to be able to help you here. You could try taking a thread dump of the process (PID 1236 in the image above) to identify why the JVM that's performing AOT processing has not exited. I suspect that there's something in the application that is starting a thread that prevents the JVM from exiting. I'll close this one for now as it isn't actionable. We can re-open it if a sample is provided.

[8502596]

sample

This is the submitted sample, most of which contains source code. The key part may lie in Shiro Config. java. Unfortunately, there may be other components such as quartz that could cause it to get stuck It is precisely because the process oot of the Spring Boot Maven plugin did not provide any error information that this issue occurred.