About concurrency

51-60 of 110Refresh
Issue
1

InternalException during producer/consumer scenario

.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1177) at java.util.concurrent.Semaphore.acquire(Semaphore.java:272
Issue
1

InvalidClassException

.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor
Forum
1

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04] at java.util.concurrent.ThreadPoolExecutor
Forum
1

locks on pure query activities

a new build (2.7.1_01) that supports concurrent reading from the database file. To enable the new ... ("objectdb.temp.concurrent-file-read", "true"); (or using the -D JVM argument). It is unclear
Issue
1

Negative snapshot user count

) at rbccm.digest.workflow.manage.WorkflowManager$1.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor
Issue
1

NullpointerException at a normal select

.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run
Forum
1

NullPointerException while setting a new property value

version). In my theory, this is a (possible) cause and what we are doing - concurrent access ... must not be shared among multiple concurrently executing threads, as the entity manager and persistence
Forum
1

Occasionally slow requests in load testing

be able to handle the load. Are you sure about that? More than 10-20 concurrent working threads ... concurrent working threads may cause more harm than good. If you change it to 20 you can still use
Forum
1

OptimisticLockException

that has been concurrently changed by someone else. If it is not acceptable then refresh is not the solution ... to the user if it tries to commit changes on a document that has been concurrently changed by
Forum
1

Performance tuning, best practices

of several concurrent clients, or maybe same slow performance is also for a single user with that specific operation? ObjectDB can use multiple cores to serve concurrent requests from different users