Deadlock while creating a new thread on bean initialization with transactional code invocation [SPR-14388] #18961
Comments
Juergen Hoeller commented This is quite analogous to the recently fixed #18814 but in a separate AOP code path. In any case, fixed for 4.3.1 now, and to be backported to 4.2.7 (and later on to 3.2.18). Please give the upcoming |
This was referenced Jan 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bartosz Popiela opened SPR-14388 and commented
Is it a Spring TX bug or a client code should take care of this situation?
As a workaround I added```
depends-on="org.springframework.transaction.interceptor.TransactionInterceptor#0"
Affects: 3.2.17, 4.2.6, 4.3 GA
Issue Links:
Referenced from: commits 0d3a22c, fd9d518, a1c0987
Backported to: 4.2.7, 3.2.18
The text was updated successfully, but these errors were encountered: