About concurrency

31-40 of 112Refresh
Forum
2

Potential ObjectDB bug

.Final.jar:1.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_77] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java ... .Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0
Forum
2

Weird behaviour with enhanced classes and embedded entities

.ArrayList; import java.util.List; import java.util.concurrent.LinkedBlockingQueue; import java.util.concurrent.ThreadPoolExecutor; import java.util.concurrent.TimeUnit; import javax.persistence ... An EntityManager is not designed to be used concurrently by multiple threads. The recommended way to implement
Issue
2

Null pointer exception being thrown from within ObjectDB.

.HousekeepingProcess.run(HousekeepingProcess.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent
Issue
2

Query fails with failed to read

.concurrent-file-read" is enabled. Are you using "objectdb.temp.concurrent-file-read ... - we are using the concurrent file read (System.setProperty("objectdb.temp.concurrent-file-read", "true
Forum
2

Entity is not related to ObjectDB, but i get exception from ObjectDB

(ReverseAjaxHandler.java:95) [dp.transfer-1.0-SNAPSHOT.jar:1.0-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor ... ) [rt.jar:1.7.0_45] Caused by: com.google.common.util.concurrent.UncheckedExecutionException: javax
Issue
2

InternalException: null

Hi! when I run my application where 10 threads are concurrently accessing ObjectDB (only reading ... .extech.serverImpl.QuantServerImpl$6.run(QuantServerImpl.java:2184) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker
Forum
2

Many connections possible? and will it makes problem in future?

concurrently ? Does it have queue and cache ? 2-) is it dangerous to use that system on many online users ?   Having 200,000 concurrent threads is probably a bad idea. Usually this should be handled by ... . ObjectDB doesn't limit the maximum number of allowed concurrent connections, but they are limited by
Forum
2

Mismatch client-server protocol prefix

-server communication. It could be because of concurrent use of the same connection and sockets (i.e. same EntityManager) by two concurrent threads. ObjectDB synchronizes use of EntityManager by different ... concurrent use of the same EntityManager in different threads. How can #2 happen? We are persisting
Forum
2

RT Java application recording into 100DB run OOM after a few hours.

.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent ... , so it can easily exceeds your VPS RAM. If you must keep 100 databases open concurrently then you will have to reduce cache sizes, etc. EKK
Issue
2

Unexpected error when loading all entity instance

concurrently by two different processes directly (i.e. not using one server process)? Do you move or ... is somehow accessed concurrently by two instances of ObjectDB (e.g. two separate class loader contexts in the same ...  concurrent access by different processes, but the lock may not be effective on some systems, or in the same