ObjectDB Database Search

Verify Error with Java 1.7

with the @Embedded annotation, requiring ObjectDB to verify that the type is indeed embeddable: @Entity

. It is the application's responsibility to verify that when an object is stored in the database, the entire closure

your database files before renaming or moving persistable classes and you must verify that after such changes

section and verifying system and server integrity). Cookies can be "Persistent" or "Session" Cookies

The ObjectDB Doctor tool provides two related services: Diagnosis and validation of an ObjectDB database file Checks a given ObjectDB database file, verifies that it is healthy and valid, and if the file is not valid (it is corrupted), produces a detailed diagnosis report of all the errors. Repair

Using these Keystore and Trustore files a client can verify during SSL handshaking

; Next . Verify that the Create a simple project checkbox is disabled and click Next . Enter  ... folder: Note: You should verify now that Maven Integration for WTP is installed, by right clicking

, select New File , enter persistence.xml as file name and click Finish . Verify that a new

We start by creating a new NetBeans Project: Open the [New Project] dialog box, e.g. by using File New Project... Select Java Java Application and click Next . Choose a Project Name (e.g. Tutorial ). The name of the Main class should be tutorial.Main . Verify that exactly this case sensitive fully

; Finish . Verify that a new persistence.xml file was created as shown below: Finally, use  copy

Paul Edwards Please verify that your objectdb.conf file is used by the server. The activation setting ... that contains the revised configuration. To verify that the configuration is really used by the server - add ... :199) This is not good!   dmoshal David Moshal Verify that after the upgrade you are still using

installer, instead I just unzipped it in a logically named directory. (3) Verify maven 3 is installed and verify it works fine from eclipse using the maven build command to do a jetty:run command. Point ... eclipse/tomcat 6. Please verify that you can run the Guestbook app from eclipse and single step

which methods it is true and in which false? In addition, verify that the same EntityManager is used ... at least on my computer. Please verify that you switched the server and the client (in pom.xml) to 2.0.5

addition, please verify that you close the database with PersistenceManagerFactory's close ... , please verify that you close the database with PersistenceManagerFactory's close

management changes - on order to verify that the new problems are caused by the new changes. support ... dump to verify that this is the same problem? Hopefully, using your UTC (#19) the fix

. Please verify that the same versions of all the entity classes are used by all the parts ... .5.3_03) to verify that this is not an issue that has already been fixed

you have to verify that the configuration is updated on both the server and the client side. In ... ;deliberately to the objectdb.conf file and restart the server, to verify that the  file is in use by

them. When a circular lock is found, we should be able to fix the deadlock. If you can verify

this is the only EntityManagerFactory instance in your application verify that emf.close is indeed reached and executed (e.g

exception stack trace. What is in line 28 at that class?   Please also verify that you close

; @OrderBy , and actually any change to your schema may cause a similar exception. Please verify

hi, my current use case is: execute unit test, verify results in explorer. my problem, i have to close the explorer before every run, and open it again after the tests are done. this slows down the whole process. i opened the database in readonly mode, but the file will be locked by the explorer

boolean verified = false; public RequirementDBEntity() { } RequirementDBEntity(String reqID, String

). Other ideas: verify that both servers on 6136 and 6000 are running, start with an empty database or

that you must verify that id collision is avoided and every entity object gets its own unique id). support Support

the application does not help.   Also, dbDoctor does not fix the problem. You can verify this by

Thanks for your help.  I did run activation on the machine and did just want to verify that I

running threads indicate that there are 3 open databases. Verify

initialization. I've also verified the data using ObjectDB Explorer. Here's the whole stacktrace: com

;(and eliminate these exceptions) but first verify that the exceptions do not indicate a problem in

Dev Could you please verify that this setting is in the correct  objectdb.conf file? As

; private String description; private String reqID; private boolean verified = false; //Constructor

, however, uses an older version (2.2.5). Please verify that you do not have references to older

. Seems unrelated to ObjectDB. But maybe you should verify first that the exception is thrown where you think

that way!    mHornbach Michael Hornbach Just verified that the problem is fixed here in

in your project that fails. If an exception is thrown - verify that you get the stack trace (e.g

in advance for your help. Best wishes, The BTC-ES Team btc_es BTC EmbeddedSystems Please verify ... class loader or multiple class loaders? Please verify that you close every EntityManager

the database (from post #13 above) after this action we can verify that it contains statistics as

package; you can verify that it is being read at run-time by introducing an error such as an invalid

verified now by a search in the entire ObjectDB source code (calls to gc were found only in our tests

, which could possibly happen due to an unknown server failure. The database file will not help here, but just verify

anymore in build 2.2.6_01. Please verify that: You are using only the new ObjectDB jar and the old jar

, when an object for merge has an unexpected type. Could you please verify that you were passing an entity object

(and then verify the fix by using the Doctor in diagnosis mode). Check if your application can bring

Currently ObjectDB doesn't prevent deletion of entity objects that are in use and referenced by other entity objects, and it is the application responsibility to avoid such deletion. During development and testing it is recommended to use the ObjectDB Doctor to verify

reason is unknown. You should check your database with the Doctor to verify that the database file

and we use tests (on every build of ObjectDB) to verify that large objects work well. Unfortunately

that this issue only occurs, when a first query is present (lines 36-39). Can you please verify

again (if not moved without the recovery file). Please verify that recovery is enabled and report