About failure


Optimistic lock

Hello When I get an optimistic lock on an object, refresh(), start trans and persist?  Will the changes made to the object before the violation be retained or must they be duplicated in the retry code?  Assuming it affects only one object.  tia. ... By default, objects after transaction failure (regardless of cause) retain their values in memory. Objects ...



... Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding an entity after a ...


Remove not working

Hello! We have a strange problem. ... I make a mistake, or is this configuration showing a true failure? import javax. jdo . JDOHelper ; import javax. ... If I manually set ignoreCache=false to correct the failure above, then the test succeeds. ...


"Attempt to lock a non entity object" error

Probably a simple answer for someone who's been using ObjectDB for awhile: I'm reading objects from the database outside a transaction (inside doesn't seem to matter). First cycle of doEdit and then doCancelEdit works fine. Second time I doEdit produces the error "Attempt to lock a non entity object" session.rollback() is somehow causing the problem (found through debugging) Is this enough information for someone to suggest what might be happening and how to fix it? ... - either by invocation of rollback or by a commit failure." Quite different behavior from what I expected and would ...


How to upgrade from ObjectDB 1.0?

Explains how to upgrade from ObjectDB 1.0 to ObjectDB 2.0.... in ObjectDB 2.0: ObjectDB 2.0 is more sensitive to failure to close a PersistenceManagerFactory . The database is closed ...



A root type in the from clause.(Interface of JPA)



The PluralJoin interface defines functionality that is common to joins to all collection types.(Interface of JPA)



Type for query expressions.(Interface of JPA)


OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011)

I might also be seeing a failure of my OEM license when using ObjectDB 2.7.2_03. [ObjectDB 2.7.2_03] javax.jdo.JDODataStoreException Too many persistable types (>10) - exceeds evaluation limit (error 1011) at com.objectdb/com.objectdb.jdo.JdoQuery.compile(JdoQuery.java:734) I will have to investigate more tomorrow (but I want to submit this now due to timezone differences and weekend for perhaps faster response/resolution if it is an ObjectDB issue). ... I might also be seeing a failure of my OEM license when using ObjectDB 2.7.2_03. [ ...


Large query parameter - out of memory

I have an entity object composed of an id, large data in the form of a string and the hashcode of the string as an index. The attached test saves 2000 of these objects, writing the data to a txt file as it goes. It then loops through the data from the file and queries for the entity id based on the data hashcode and the data itself. ... Your test demonstrates a failure of ObjectDB in evaluating cached query result size. Since Java ...