ObjectDB ObjectDB

Internal Website Search

1-10 of 130 resultsRefresh
181

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+1
181

Optimistic Lock Exception With No Concurrency

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

Lock prevents PersistenceManager.close when retainValues = false

.run(TCPTransport.java:682) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor ... : - locked <c00712> (a java.util.concurrent.ThreadPoolExecutor$Worker) "RMI TCP Connection(5
22

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
13

Database Management Settings

specifies the maximum number of concurrent threads that can be served by the database engine simultaneously
13

Setting and Tuning of JPA Queries

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

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
7

Freeze during save

$ConnectionHandler.run(TCPTransport.java:682) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run ... synchronizers: - locked <ff9a15> (a java.util.concurrent.ThreadPoolExecutor$Worker) "JMX server
4

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 ... $SocketProcessor.run(JIoEndpoint.java:312) at java.util.concurrent.ThreadPoolExecutor.runWorker
3

javax.persistence.Version

javax.persistence Annotation Version Target: Fields (including property get methods) Specifies the version field or property of an entity class that serves as its optimistic lock value. The version is used to ensure integrity when performing the merge operation and for optimistic concurrency

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support