About concurrency

1-10 of 123Refresh
Manual
77

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
Manual
62

JPA Entity Fields

Explains how to define and use primary keys in JPA, including composite and embedded primary keys.
Forum
36

Optimistic Lock Exception With No Concurrency

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

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
Manual
15

Database Management Settings

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

Setting and Tuning of JPA Queries

uses automatic optimistic locking to prevent concurrent changes to entity objects by multiple users
Issue
9

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
6

Lock prevents PersistenceManager.close when retainValues = false

) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang ... .concurrent.ThreadPoolExecutor$Worker) "RMI TCP Connection(5)-192.168.1.142" - Thread t@23
Forum
5

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
5

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