About check


ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

The following error is reported for objectdb-2.6.9.jar: Failed to commit transaction: Failed to set numeric value of field property com.greensoft.objectdb.test.entity.Element.id using reflection (error 613) Did not happen with objectdb-2.6.3_04 (which one can easily test and compare in the test console app for NetBeans8.1 provided, as explained below). To reproduce download the app and unpack, open in NetBeans8.1, perform Clean and Build, and Run: ... to modify a primary key" exception is thrown due to a check that was not expected to be performed for a direct access by ObjectDB. ... supports an option to disable the "Enhancement ... is old" check and error: System. setProperty ( "objectdb.temp.no-enhancement-crc-check" , "true" ) ; Set the property before accessing ...


Locking in JPA

Explains how to use optimistic locking and pessimistic 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 da ...


High availability and other pratical questions

Hi,   I've just started developing a mobile app which will use a server side, hopefully handling a lot of processing and traffic. I was inteding to use TomEE+ with built-in OpenJPA and Postgres DB, initially on one master server but as it grows more master servers will be set (in different geo locations/data centers) using some data sync mechanism between them.   Now that i've met ObjectDB I want to check the option using it instead of postgres so I have few questions regarding it: ...   Now that i've met ObjectDB I want to check the option using it instead of postgres so I have few questions regarding ... for replaying) is relatively low, but you will have to check it with your own application. ObjectDB Support ...



PersistenceManager is the primary interface for JDO-aware application components.(Interface of JDO)


Failed to read the value of field using reflection (error 363)

I have encountered this error from one of the many servers hosting my application. Other servers didn't encounter errors of this kind and running without problems. My system provider said that nearly all of the servers are VM-based including this one which encountered this error. It is the 'youngest' server in deployment. I can get more information as you require. As the application developer, I am perplexed as I have use JPA and ObjectDB for years now. I could use your assistance in overcoming this problem. Thank you. ----- ... the last ObjectDB version. It is also recommended that you check the database file with the ObjectDB Doctor, and use it to fix the ... ObjectDB version (2.5.4_03)? In addition, please check the database with the ObjectDB Doctor and post the results. ...


Problem with distinct select, order by and equivalent alias/attribute path

Hi, while working with a (standard-)JPA-query generating framework we run into an exception when ordering the results of some projection when the order by expression is different (though logically equivalent) to the projection expression. Here is the example: ... as the "correct" solution would suggest. Could you check these issues again? edit ...



Make the parameter instance persistent in this PersistenceManager.(Method of javax.jdo.PersistenceManager)


multi thread application, id field sporadically null

We are testing objectDB with a multi thread application. Each thread has it's own entityManager created from a common factory. In one thread we receive sometimes an object from the database with the field that is declared as @Id having the value null (what is not correct, we checked that with the explorer). The class is declared like this: ... ... which is a new object that has no id yet. You may want to check if using a new EntityManager with an empty cache makes a difference, ...



Hi, I've been getting the following exception when trying to query ObjectDB in server mode version 2.3.4_05. ... doesn't help, try to use the ObjectDB Doctor, first to check the database and then to fix it. If it doesn't help - you may have to ... supposed to be all using the same classes. I'll double check.   Thanks, Eitan ...


spuriously objectdb objects have null references

from time to time we have in a multi threaded environment objects where all the references are null (i.e. references actions, childNodes), even after a subsequent refresh. we are using a separate entityManager per thread and have a central point where we encapsulated all the needed entitymanager methods and protected them with synchronized like:   ... ... only for lazy collection fields? Could you please check the status of the entity objects and these collection fields when this ...