Internal Website Search

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

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

500Mb ObjectDb database opening issue

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

instructions (that have been verified by you first) how to reproduce it. As already explained

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

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

. Please verify that you changed the correct configuration file. If you have separate configuration files

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

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

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

constantly, and one client may see an object with a version that it doesn't know yet. Please verify

cannot be opened by more than one user (process / class loader) simultaneously. Please verify

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

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

The stack trace indicates that an attempt to access the JDO dtd file (in order to verify

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

: ... Please verify that you only have objectdb.jar in the classpath and not odbee.jar , which is an old

more than once and loaded more than once (by different class loaders). Please verify that all the relevant

Hi,    I've got a simple JPA2 Criteria query which fails when doing an object equality. I verified this against EclipseLink and over there, it works. I'll Attach some code snippets to help figure it out:   @Entity() public class Product{ . . . @ManyToOne     private

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

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

PositionReportBeans in reports. I can verify with the ObjectDB explorer that all of the data

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

; natmaclin Natalia Levine You should also verify that resizing doesn't cause defragmentation. Using

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

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

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

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

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

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

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

client-server mode - verify that you changed the configuration on the client side. support Support

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

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

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

classes anyway to improve performance). support Support Verified and confirming that 2.2.8_01 fixes the issue. kaosko Kalle Korhonen

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

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

. 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

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

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