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
Replace synchonized
block with ReentrantLock
to make virtual thread friendly
#4510
Comments
hello @ikhoon I would like to work on this issue |
We need to fix all classes in Armeria that use
We may start with |
thank you kindly |
I'm also willing to do a part if it's welcome 😄 |
glad to work with you!! @j-min5u 😆 |
@Bue-von-hon Sure 😸 |
If all migration has finished, it would be worth prohibiting |
I'll do |
ok I'll replace under |
Motivation: synchronized should be removed because they should be avoided when using virtual threads resolves part of #4510 Modifications: - Replaced all _synchronized_ under core/client package with ReentrantLock
Motivation: for virtual threading, we should replace synchronized with reentrantLock resolves part of #4510 Modifications: - replace all synchronized with reetrantLock under `common/util`
Motivation: for virtual threading, we should replace synchronized with reentrantLock resolves part of line#4510 Modifications: replace all synchronized with reentrantLock under core/common
@Bue-von-hon @j-min5u joining you guys here. what other module are yet to be done? |
@daniel-itunu I'm working on a common module right now.🙂 |
|
@daniel-itunu we're currently working on the core module. you could work on other modules like |
Motivation: for virtual threading, we should replace synchronized with reentrantLock resolves part of #4510 Modifications: replace all synchronized with reentrantLock under `core/common` Result: no more synchronized blocks on `core/common` Co-authored-by: Trustin Lee <trustin@linecorp.com>
There is a current known limitation that code should avoid using a synchronized block for the virtual thread.
Related work:
The text was updated successfully, but these errors were encountered: