ObjectDB ObjectDB

Internal Website Search

81-90 of 198 resultsRefresh
17

Degrading performance overtime

to see considerable degrade in performance caused internal objectdb locking: "pdncrttorfo42-WSAgent-1 ... ) - waiting to lock <64c56ec3> (a com.objectdb.o.PGC) owned by "ODB-FileWriter" t@116 at com ... .ah(SFL.java:998) - locked <75608da2> (a com.objectdb.o.LFL) at com.objectdb.o.MST.ah(MST.java:1746
3

LockModeType.OPTIMISTIC_FORCE_INCREMENT

Enum Constant javax.persistence.LockModeType OPTIMISTIC_FORCE_INCREMENT Optimistic lock, with version update. Since: JPA 2.0
3

javax.persistence.LockTimeoutException

: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs that does
3

setHint(hintName, value)

on the standard timeout hint. Depending on the database in use and the locking mechanisms used by
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
3

setHint(hintName, value)

timeout hint. Depending on the database in use and the locking mechanisms used by the provider, this hint
3

javax.persistence.PessimisticLockException

Interfaces: Serializable Thrown by the persistence provider when an pessimistic locking conflict occurs
3

Query fails with failed to read

has locked a portion of the file" shows some results that may be relevant, for example: https ... -cannot-access-the-file-because-another-process-has-locked-a-portion-of-the-file-57?forum=visualstudiogeneral If the answer on that thread is correct then the locker is another process, i.e. this is not a lock
0

getOptimistic()

Method javax.jdo.Transaction boolean getOptimistic() Optimistic transactions do not hold data store locks until commit time. Returns: the value of the Optimistic property. Since: JDO 1.0
0

setOptimistic(optimistic)

Method javax.jdo.Transaction void setOptimistic( boolean optimistic ) Optimistic transactions do not hold data store locks until commit time. If an implementation does not support this option, a JDOUnsupportedOptionException is thrown. Parameters: optimistic - the value of the Optimistic flag. Since: JDO 1.0

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