Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Threading issues causing apparent deadlock [SPR-11418] #16045

Closed
spring-projects-issues opened this issue Feb 11, 2014 · 1 comment
Closed

Threading issues causing apparent deadlock [SPR-11418] #16045

spring-projects-issues opened this issue Feb 11, 2014 · 1 comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process

Comments

@spring-projects-issues
Copy link
Collaborator

chip stettler opened SPR-11418 and commented

I have two beans that implement @Async methods. I have an async method in bean #1 calling an async method in bean #2. I create A ThreadPoolExecutor with 5 core threads, 10 max threads and 25 queue length.

I created a test that creates 5 parallel calls to bean#1 async method. The threads appear to deadlock and a timeout occurs on the Future.get(). If I increase the core threads to 6 the test executes with no problem.

If I remove an @Async from either bean so that there is no nesting of async calls then everything works fine.

Seems like a bug as it sort of works if there are enough threads but the queuing aspect of the thread pool seems to break when nested.


Affects: 3.2.4

Attachments:

@spring-projects-issues spring-projects-issues added type: bug A general bug status: waiting-for-triage An issue we've not yet triaged or decided on in: core Issues in core modules (aop, beans, core, context, expression) and removed type: bug A general bug labels Jan 11, 2019
@rstoyanchev rstoyanchev added status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jan 11, 2019
@spring-projects-issues
Copy link
Collaborator Author

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: bulk-closed An outdated, unresolved issue that's closed in bulk as part of a cleaning process
Projects
None yet
Development

No branches or pull requests

2 participants