About concurrency

1-10 of 110Refresh
Forum
31

Recommendation - concurrent access multiple class v

, then finally all of them get the new version? So...basically...concurrent access with version x and version x
Forum
31

Optimistic Lock Exception With No Concurrency

during this process. What could cause this exception, knowing there couldn't be any concurrent
Manual
13

Database Management Settings

specifies the maximum number of concurrent threads that can be served by the database engine
Manual
13

Setting and Tuning of JPA Queries

uses automatic optimistic locking to prevent concurrent changes to entity objects by multiple users
Manual
13

Locking in JPA

JPA 2 supports both optimistic locking and pessimistic locking. Locking is essential to avoid update collisions resulting from simultaneous updates to the same data by two concurrent users. Locking in ObjectDB (and in JPA) is always at the database object level, i.e. each database object is locked
Issue
8

Freeze during save

.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run ... .concurrent.ThreadPoolExecutor$Worker) "JMX server connection timeout 74" - Thread t@74 java.lang
Forum
4

UserException: Invalid configuration in 'internal' - Check permissions

.server.node.NodeTaskWrapper.run(NodeTaskWrapper.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util
Issue
4

stress test -> com.objectdb.o.InternalException: null

.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker ... (JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java
JPA Doc
4

javax.persistence.LockModeType

and there is a high likelihood of deadlock or update failure among concurrent updating transactions. The persistence
JPA Doc
4

javax.persistence.Version

javax.persistence Annotation Version Target: Fields (including property get methods) Specifies the version field or property of an entity class that serves as its optimistic lock value. The version is used to ensure integrity when performing the merge operation and for optimistic concurrency