Internal Website Search

of the merge. Still haven't used ObjectDB in embedded mode. My issue was concurrency , and as OP posted, they are mainly single threaded. Willks William

Hello All, Can objectdb handle client - server connections from over 200 users? Can it be efficiently used in client-server mode? Code examples where possible will be appreciated. Thank you. Regards kaybel ebele ObjectDB can handle concurrently 200 users (or more). The maximum load

of an object. To avoid using the same object by different users concurrently (even for read

? A separate cache is managed per open database. How many database files do you use concurrently

with ObjectDB along with Concurrency controls and transaction mgmt. Let us know if it is possible to run

there are other feature requests with higher priority. True, I concurr that IT WORKS. However consider the bloat

of entity classes concurrently . When you upgrade your schema you must make sure that the ObjectDB

. If you only use small databases, not too many concurrently , and with no other activities

/PersistenceManager level. To have real concurrent operations, you have to use ObjectDB 2.0 (and not ObjectDB 1.0

. Alternatively, you may also try reducing concurrent memory consumption by using less working threads  

of using more than one version of an entity class concurrently . When you restart the server

production (see this stackoverflow thread ) and can serve 200 or more concurrent connections in client-server mode. support Support

; OptimisticLockException  is thrown when that version number indicates a concurrent update by another user (using

that the whole issue could be delegated to the container? I'm concurrently developing actively

Hello, it is possible to use an entity attribute of type java.util. concurrent .ConcurrentHashMap Your web site http://www.objectdb.com/object/db/database/features 'Object Model & Data Types' has no guidelines about this data type. Best regards btc_es BTC EmbeddedSystems You can persist a Map field

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

Hi, we are using Embeded objectDB 2.4.4_06 in a highly multithreaded concurrent manner and we have noticed a performance problem in our application that seems to be attributed to ObjectDb's internal locking. When profiling our app in JVisualVm we notice a large number of threads are blocked

this case. It may be possible to improve performance by tuning the configuration (e.g. the maximum concurrent threads ). support Support

databases with JPA and JDO concurrently . The use of API does not affect the database file format. support Support

is locked for a single process. Use client-server mode or embedded-server mode to enable concurrent

the discussion: Use issue #2087  to discuss using a large number of concurrent open databases

Fixed unstable  activation issues. Fixed  issue #2954  - using IS NULL (or == null) on parameters in queries. Fixed automatic schema update on renaming or moving an enum type. Fixed issue #2964  (critical) - concurrent update of large objects with version-check=false.

. Our system has a load of around 400 concurrent webSocket connections that normally only query (without updates

open databases do you use concurrently ? Following the thread dump I count about 9 open databases

versions with the concurrent read queries that have been solved for us with that version. We double

of reflection mode (no enhancement) by minimising  tracking backups. Improved concurrency by using

the database by a concurrent thread while the query was executed? Any other details regarding

). Fixed a NullPointerException on concurrent access of first object of an entity class. Fixed bug

an option for possibly improved concurrent database file access. Added automatic logging of query details

EntityManager and its factory concurrently . Solved a possible issue with closing the ODB-WeakRefPurger daemon thread.

EntityManager and its factory concurrently . Solved a possible issue with closing the ODB-WeakRefPurger daemon thread.

and about 100 concurrent threads reading and writing to the DB per second. Thanks Trianglehead Json