Fast Object Database for Java - with JPA/JDO support

Internal Website Search

71-80 of 90 resultsRefresh
3

again merger missing logs + objectdb exception

to remain healthy). It shows that this happens when an optimistic lock exception is thrown during commit ... of optimistic lock exceptions, which should fail regardless of printing their location now to the log. support ... when there is an optimistic lock exception on a large object (>= ~2KB). Assuming you have ObjectDB 2
2

ObjectDB 2.4.0

classes (issue #672). Fixed LockModeType.OPTIMISTIC (READ) by handling it as OPTIMISTIC_FORCE_INCREMENT. Fixed a bug in optimistic locking on find by using LockModeType.WRITE. Fixed exception
2

Error during closing an entity manager

and with this one we get an optimistic lock exception without enhancement. If we enhance all entities then the issue does ... changed the exception from the one in #3 above to an optimistic lock exception. More information ... be your priority now. support Support We have found the reason of the optimistic lock exception and we fixed
2

Query in nested transaction returns detached entity if lazy-loaded

= 1) and committed, during the commit an optimistic lock exception is thrown. The version flag ... to commit transaction: Optimistic lock failed for object com.btc.ep.base.bl.internal.entities.mapping ... .java:311) ... 45 more Caused by: com.objectdb.o._OptimisticLockException: Optimistic lock failed
2

Pessimistic lock

: javax.jdo.option.Optimistic=false javax.jdo.option.NontransactionalRead=true javax.jdo.option ... Now we use the following options in DB2: javax.jdo.option.Optimistic=true javax.jdo.option ... =true javax.jdo.option.RestoreValues=false The DB2 returns the message "Optimistic lock failed
2

Failed to commit transaction: Attempt to commit a rollback only transaction

Moshal note: optimistic locking is off dmoshal David Moshal update 1: problem persists if optimistic
1

ObjectDB 2.6.5

specified in configuration. Fixed optimistic lock exception on removing of a flushed modified
1

Replication error on slave restart

: Optimistic lock failed (see multiple nested exceptions) at com.objectdb.o.MSG.d(MSG.java:61
1

Transaction isolation support?

of that specific object using the first EntityManager, due the default optimistic locking (unless
1

Entity Version History

ObjectDB manages automatic entity versioning (for optimistic lock purposes). Every entity object modification is reflected by a new version number. Naturally, previous values in the entity object that are overridden by new values are discarded. Some applications may benefit from the ability

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