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

Correctly pass executor to CompletableFuture Async calls. #6905

Open
sachin-j-joshi opened this issue Oct 5, 2022 · 0 comments · May be fixed by #6906
Open

Correctly pass executor to CompletableFuture Async calls. #6905

sachin-j-joshi opened this issue Oct 5, 2022 · 0 comments · May be fixed by #6906

Comments

@sachin-j-joshi
Copy link
Contributor

sachin-j-joshi commented Oct 5, 2022

Describe the bug
When CompletableFuture.thenComposeAsync is called without specifying executor the task runs on default thread pool which is incorrect.

Instead, always call overload that explicitly takes executor.

To Reproduce
This was recently observed in longevity test.

Screenshots
Below is list of relevant calls

image

image

Additional information
Add any other information about the problem here, including the root cause if known.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant