We ran into the issue that the org.springframework.transaction.config.internalTransactionAdvisor was still in creation while a service annotated with the transactional annotation was created thus not getting a proxy att runtime. (See also this issue as well as the comments: https://github.com/spring-projects/spring-framework/issues/15063#issuecomment-1588914665)
Please provide a solution to make sure that all needed advisors are generated before the beans depending on them.
This issue appeared first after upgrading from Spring 5.3.x to Spring 6.08
Comment From: linuxmin
Any thoughts on this issue yet? Maybe @wilkinsona or @jhoeller? Or is there already a built-in solution to come around this issue without having to go with the lazy annotation or depends-on workaround?
Comment From: snicoll
Please provide a solution to make sure that all needed advisors are generated before the beans depending on them.
Unfortunately, it is not as easy as it may sound like. There are various factor to consider. If you have cyclic dependency, please be aware this isn't a recommended setup and the core container works in "best effort" mode so it might not be able to apply all aspects. When doing so, it logs a warning.
If you want support, please take the time to prepare a minimal sample that reproduces the problem you've described. You can attach it to this issue as a zip or push the code to a GitHub repository.
Comment From: spring-projects-issues
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Comment From: linuxmin
Thank you, I will try to create a small reproducable example because i am not allowed to provide the original code
Comment From: snicoll
Thanks. We don't need the original code, the simplest form that reproduces the problem you've described.
Comment From: spring-projects-issues
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
Comment From: linuxmin
I cannot give a reproducable example because i do not know how to reproduce this on a smaller scale, but even debugging or configuring a parameter which leads to an exception on startup would be helpful to avoid unexpected runtime behaviours. Would that be a possible solution?
Comment From: snicoll
Unfortunately, we can't really research that solution if we're not able to figure out what problem you're facing. You should get a log that the bean couldn't be post processed.