About concurrency

91-100 of 111Refresh
Forum
1

Optimistic locking failure

Optimistic locking failure: I am using a Semaphore to force this execution of concurrents transactions T1 and T2 that cause parallel updates to A/B but it does not throw an OptimisticLockException and roll back. T1 T2
Forum
1

OptimisticLockException

was concurrency, and as OP posted, they are mainly single threaded. dmoshal Willks
Forum
1

Out of memory

and that may decrease the application performance. Alternatively, you may also try reducing concurrent
Forum
1

Performance in large transactions

them with other concurrent updates. Attached a new Example in single class format:   import java
Forum
1

Pessimistic Lock Timeouts setting

locking due to a highly concurrent system that requires integrity on some value. Rest assured
Forum
1

Query and commit simultaneously

. To have real concurrent operations, you have to use ObjectDB 2.0 (and not ObjectDB 1.0
Forum
1

Remove an entity which attributes were changed - OptimisticLockException

a concurrent update by another user (using another EntityManager). According to your description
Issue
1

Server out of memory exceptions

. How many open databases do you use concurrently? Following the thread dump I count about 9 open
Forum
1

Transaction isolation support?

the same object by different users concurrently (even for read) you can use explicit locking
Forum
1

Unable to store AtomicInteger

In the docs, all serializable types should be persistable. However, when I tried to persist a field of type AtomicInteger, I got the following message: Message: Failed to commit transaction: Attempt to store an instance of a non persistable type java.util.concurrent.atomic.AtomicInteger I am using