-
Bug
-
Resolution: Done
-
Blocker
-
3.0.1.Final
When operating concurrent clients that create lots of nodes, not all nodes are properly saved. There are no problems when using a single client.
We have a created a test web app that receives json as data and saves that json as nodes and node properties. We have reproduced the problem both with infinspan configured with file cache and berkeley db cache. We have reproduced it both with infinispan configured to use OPTIMISTIC and PESSIMISTIC locking mode with a berkeley db cache.
See the comments for the details.