Internal Website Search

pessimistic locking only? I've tried various xml configurations, and also various transaction ... , that setting is for optimistic locking. My question was about pessimistic locking (specifically, pessimistic write locking). Your documentation seems unclear about that.   dmoshal David Moshal

Probably a simple answer for someone who's been using ObjectDB for awhile: I'm reading objects ... .getSelectedValue(),       LockModeType. PESSIMISTIC _WRITE); . . } //doEdit ... , LockModeType. PESSIMISTIC _WRITE);         System.out.println

guess I should read doco more. I ran into the same error from a pessimistically locked entity (global ... . Also have the Explorer open Questions: a) what is it about? b) is there a setting for pessimistic mode? In my app ... on pessimistically tracked entity.   Modified conf file, and got the test case working perfectly.  

; support Support A possible solution (which is currently not implemented) is to use pessimistic locking ... want to use Pessimistic Lock as a way of enforcing a cluster wide singleton of services, a pessimistic ... adds automatic release of pessimistic locks on client-server disconnection. The locks

and roll back. T1 T2 ---------------------------------------------------------- READ (A) version=1 value=0 | READ (B) version=1 value=0 | | READ (A) version=1 value=0 | READ (B) version=1 value=0 | B ... Thread[Thread-2,5,main] READ   A1 version=1 value=0 Thread[Thread-2,5,main] READ   B2 version=1

.InternalException: Error reading UTF string at com.objectdb.o.BYR.U(BYR.java:1217) at com.objectdb.o.BYR.U(BYR.java ... ) WARNING: javax.ejb.EJBException: Error reading UTF string at com.sun.ejb.containers ... .run(Thread.java:829) Caused by: com.objectdb.o.InternalException: Error reading UTF string at com

on read , is desired, should I use optimistic=true to get more concurrency?   CBE CBE All relevant ... a queue) you will need multiple  PersistenceManager instances. In ObjectDB 1.x pessimistic locks

. ObjectValue ID:=100, TYPE:=Person, REVISION:=0, isPersisted:=true, LockMode:= PESSIMISTIC _WRITE ... . ObjectValue ID:=100, TYPE:=Person, REVISION:=2, isPersisted:=true, LockMode:= PESSIMISTIC _WRITE

Is it possible to change a LockTimeout for  pessimistic  lock? glaz Alexandr Kurucin Currently ObjectDB throws a LockTimeoutException immediately when a pessimistic lock cannot be granted. Future versions will support timeout setting. You may fill a feature request to increase the priority of this feature.   support Support

.URIReader. read (URIReader.java:84)         at image.URIReader.main ... 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:277) at image.URIReader. read (URIReader.java:82 ... Your code contains file reading operations that are not related to ObjectDB and may cause the problem

, do you know why? Caused by: com.objectdb.o._PersistenceException: Failed to read from file '/tmp ... .objectdb.o.UserException: Failed to read from file '/tmp/objectdb_2306457094224783100/pages0.dat ... .lang.RuntimeException: Failed to read from file '/tmp/objectdb_9120972825587144595/pages0.dat' '/tmp

.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream. read (SocketInputStream.java:171) at java.net.SocketInputStream. read (SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream. read (BufferedInputStream.java:265

Currently the slave servers are limited to read only (it is indicated at the beginning of the page ... and read to any node (and maybe such a solution will be included in a future version of ObjectDB ... that when master goes down application can only reads data? And the second question: on which level

Garris Hi! You can read more about this here:  https://www.objectdb.com/java/jpa/tool/replication The disadvantage is that slaves can be used just for reading . zmirc Mircea Chirac Hi Z, Thank you for the response. I did read the article about replication which helps with scaling reads

option, which I missed on java client side? I read https://www.objectdb.com/java/jpa/setting/ssl ... /sun.nio.ch.SocketDispatcher.read0(Native Method) at java.base/sun.nio.ch.SocketDispatcher. read ... .implRead(NioSocketImpl.java:309) at java.base/sun.nio.ch.NioSocketImpl. read (NioSocketImpl.java:350

Would this be correct?     public List read () { EntityManagerFactory emf ... . support Support The only way to do this one:   public List read () {} Is by using a Query? i.e ... you lines of code. support Support Would this be correct?     public List read

. com.objectdb.o.UserException: Failed to read from file 'C:\Users\CMOORE~1\AppDat a\Local\Temp ... to read from file 'C:\Users\CMOORE~1\AppData\Local\Temp\ objectdb_3126483439234298180\DoctorSection ... is locked for reading Try it a again also when the file is locked for reading /writing. These checks

to commit transaction: Attempt to commit a transaction in read only mode[ObjectDB 2.8.2] javax.persistence.RollbackException Failed to commit transaction: Attempt to commit a transaction in read ... ! objdbuser In ObjectDB clusters slave databases are read only (see this documentation page

.class.getClassLoader()); I read in the ObjectDB website that we can change the temp directory using ... ;system property or ..... I m using fileName.odb file to store the objects and reading objects from ... am using objectDb 1.x. i am able to set the temp folder path. When i try to read the odb.file

pessimistic exceptions, but it is more efficient to remain with optimistic locking (which is the default

JPA Enum Constant in javax.persistence.CacheStoreMode REFRESH Insert/update entity data into cache when read from database and when committed into database. Forces refresh of cache for items read from database. Since: JPA 2.0

JPA Enum Constant in javax.persistence.CacheStoreMode USE Insert entity data into cache when read from database and insert/update entity data when committed into database: this is the default behavior. Does not force refresh of already cached items when reading from database. Since: JPA 2.0

. One is to stupidly commit the transaction after a certain number of read accesses (every 10000 read access ... updates to the database or it is read only. If it is a read only operation, do you really need commit ... for posting questionable code snippets. I have repaired it. In this scenario the data is only read

JPA Enum Constant in javax.persistence.CacheRetrieveMode USE Read entity data from the cache: this is the default behavior. Since: JPA 2.0

: get data directly from the database. Since: JPA 2.0 USE Read entity data from the cache

however, married to JDO, although I think it's good. Its lack of true (before commit) pessimistic locking ... (above). I've also since starting with JDO, a couple of weeks ago, read most of the ObjectDB JPA

Added support of JPA UPDATE and DELETE queries ( issue #12 ). Added support of pessimistic lock timeout ( javax.persistence.lock.timeout ). Added implementation of the getParameters method. Added exception on pessimistic locking retrieval with no active transaction. Improved support of entity

.socketRead0(Native Method) at java.net.SocketInputStream. read (SocketInputStream.java:129) at java ... (BufferedInputStream.java:256) at java.io.BufferedInputStream. read (BufferedInputStream.java:313) at com ... . The message size going into the queue is not large - around 4k at most. Each read /write operation

Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a  NullPointerExeption on new index building

O'Hare It seems as a separate issue. Maybe related to pessimistic locking. Can you provide a test

instead of Long ) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.

UnsupportedOperationException  error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed

;in) Read this object. Read the superclass first. Parameters: in - the input Since: JDO 1.0 String

JDO Method in javax.jdo.identity.ShortIdentity void readExternal (   ObjectInput in ) Read this object. Read the superclass first. Parameters: in - the input Since: JDO 1.0

void readExternal (ObjectInput in) Read this object. Read the superclass first. Parameters: in

JDO Method in javax.jdo.identity.StringIdentity void readExternal (   ObjectInput in ) Read this object. Read the superclass first. Parameters: in - the input Since: JDO 1.0

Since: JDO 1.0 void readExternal (ObjectInput in) Read this object. Read the superclass first

, and the StateManager approves the change, then the jdoFlags field will be reset to READ _WRITE_OK

JDO Method in javax.jdo.PersistenceManagerFactory void setReadOnly (   boolean flag ) Sets the value for whether the datastore is to be considered read -only. ReadOnly set to false specifies that no updates can be performed to the datastore, and if updates are attempted

; persistent instances read in data store transactions; and persistent instances modified in

JDO Method in javax.jdo.Transaction boolean getNontransactionalRead () If true , allows persistent instances to be read without a transaction active. Return: the value of the nontransactionalRead property Since: JDO 1.0

JDO Method in javax.jdo.Transaction void setNontransactionalRead (   boolean nontransactionalRead ) If true , allow persistent instances to be read without a transaction active. If an implementation does not support this option, a JDOUnsupportedOptionException is thrown. Parameters

represents exceptions caused by an attempt to update a datastore when the PMF was created as " read

JDO Static Field in javax.jdo.Constants TX_SNAPSHOT Transaction isolation level representing the requirement to keep a snapshot for reading data. See Also: PersistenceManagerFactory.getTransactionIsolationLevel () Transaction.getIsolationLevel () Since: JDO 2.2

is restored to the state before the first change in the transaction. For persistent instances read in

instances read in data store transactions; and persistent instances modified in optimistic transactions

code. Since: JDO 1.0 void readExternal (ObjectInput in) Read from the input stream. Creates a new

, and the StateManager approves the change, then the jdoFlags field will be reset to READ _WRITE_OK. If the parameter

JDO Method in javax.jdo.identity.SingleFieldIdentity void readExternal (   ObjectInput in ) Read from the input stream. Creates a new instance with the target class name set Since: JDO 1.0

the transaction. For persistent instances read in optimistic transactions, this method allows the application