-
Bug
-
Resolution: Done
-
Major
-
7.4.0.GA, 7.4.2.GA
-
False
-
False
-
-
-
-
-
-
+
-
-
EntryWrappingInterceptor.visitPutMapCommand processes the potential expiration of keys in the input map in parallel, and wraps the entries in the context in the threads that processed the expiration response.
But NonTxInvocationContext is not thread-safe, as it uses a HashMap internally. When a PutMapCommand affects 2 or more entries can can both expire, and their keys map to the same HashMap bucket, one of the updates may be lost and the distribution interceptor will later fail with an IllegalStateException: Entry should be always wrapped!.
- clones
-
ISPN-13549 Data race in EntryWrappingInterceptor handling expired entries
- Closed
- is caused by
-
JDG-5028 Data race in EntryWrappingInterceptor handling expired entries
- Closed
- is cloned by
-
JBEAP-23095 (8.0.z) Data race in EntryWrappingInterceptor handling expired entries
- Closed
- is incorporated by
-
JBEAP-23101 (7.4.z) Upgrade Infinispan from 11.0.12.Final to 11.0.15.Final
- Closed