KITFORMA · EDITORIAL ANSWER
Why does @Async still execute on the caller thread?
KitForma editorial guide. Async annotations require enabled infrastructure and an intercepted call. A same-object call can bypass the proxy; a manually created object is not a managed async bean.
Step-by-step answer
Async annotations require enabled infrastructure and an intercepted call. A same-object call can bypass the proxy; a manually created object is not a managed async bean.
Enable the supported async configuration, inject a separate worker service and invoke its public operation through that reference. Select the executor intentionally when capacity or isolation matters. Return a future when the caller needs completion rather than assuming a void operation succeeded.
Use a latch-based test to observe caller return, worker execution and failures. Asynchronous execution is not durable job storage: process failure can lose in-memory work. A thread-name change alone does not verify completion semantics.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.