-
Notifications
You must be signed in to change notification settings - Fork 358
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
SupplierFactoryBridge#provide can cause race condition (running the CPU at 100%) #3997
Comments
hypnoce
added a commit
to hypnoce/jersey-1
that referenced
this issue
Jun 25, 2019
Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce
added a commit
to hypnoce/jersey-1
that referenced
this issue
Jun 25, 2019
Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce
added a commit
to hypnoce/jersey-1
that referenced
this issue
Jul 8, 2019
Signed-off-by: Francois JACQUES <fjacques@murex.com>
hypnoce
added a commit
to hypnoce/jersey-1
that referenced
this issue
Aug 12, 2019
Signed-off-by: Francois JACQUES <fjacques@murex.com>
pa314159
pushed a commit
to pa314159/jersey
that referenced
this issue
Aug 28, 2019
Signed-off-by: Francois JACQUES <fjacques@murex.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The disposableSuppliers field of SupplierFactoryBridge is not synchronized.
When many threads use instances supplied by DisposableSupplier, The SupplierFactoryBridge#provide invokes IdentityHashMap#put, which is not thread safe, concurrently and can cause race condition.
The text was updated successfully, but these errors were encountered: