ObjectDB Database Search

); //minutes to be added I must now sum to the dateCapture the delayMinute and verify that the current date

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

master and verifying it works as expected and the DB's are recording from the very first transaction

running threads indicate that there are 3 open databases. Verify

to use ObjectDB in your project you should probably take it for a drive test, to verify that it matches your specific project needs. support Support

in #2 junior Lekane Nimpa, Junior Please verify that both the application and the Explorer uses

API. Please try build 2.5.2_02 that will hopefully fix this issue. Unfortunately we couldn't verify

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

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

; at java.lang.Thread.run(Thread.java:722) Thanks for your help EKK EKK Emmanuel Keskes First, verify

(see below). How can I verify if the EntityManager has been successfully injected ? (statement

, but unfortunately in this case the test verified that the data is fetched with the query results

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

500Mb ObjectDb database opening issue

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

and in the class from the stack trace at least 3. Please verify that the same class version is used

flush) optimistic lock checks verify that different transactions do not conflict. This check

accesses). So a page size of 256K may work for you. But you may want to benchmark different page sizes to verify that it is the optimum setting. support Support

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

- All have been verified to be passed   Main.paygradeDB.getTransaction().begin();   this.rate = rate

temporary files. Please verify that the ObjectDB process has permissions to create directories and files

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

should show New Project (File New Project...) Also, verify that BIRT was installed by Help

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

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

. Do you have more than 10 obsolete classes? If you can verify that the exception is only thrown when an old

) Therefore, please verify that the correct configuration file is changed. Quite often changes in

Zwicker Please verify that you only use a configuration file that specifies: and also that you do not

when it is closed. Could you please verify that every  PersistenceManagerFactory instance that you open

version is highly recommended, to verify that differences between the ObjectDB versions do not break anything. support Support

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

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

Sergey This may indicate using a new server version (2.4.3_07) with an old client version. Please verify

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

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

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

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

to verify that connection that was released to the pool will not be used anymore by its previous

to follow this issue any more. I will report when I have verified it in more detail. I'll then try

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

by a Doctor check of the backup files, at least daily, to verify that the database is healthy

. Could you please verify that there is no old objectdb.jar in the classpath and you are actually using a recent ObjectDB version? support Support

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

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

) Please verify that there is no silent catch at these levels. Is it possible that the web application

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

at the enhanced class  com.btc.ep.vector.tc.internal.dmos.TCSignal ). Please verify that the same class

investigate this further. Thanks, Toby   btc_es BTC EmbeddedSystems We can now verify

then it seems that the objects are not corrupted, although it could be helpful to verify this by running the Doctor

your application recently? In that case, verify that all your classes are rebuilt and re-enhanced