Internal Website Search

_885 Pero Novaković There was a bug in UPDATE queries that was fixed . Please see this forum thread . Which ObjectDB version are you using? Try the last ObjectDB version, which should fix this issue ... them again, or use an ObjectDB version before the fix , with an UPDATE queries that change the IDs

you for this report and for the useful test case. Please try build 2.3.7_06 that should fix this issue. support Support Hi,  Thanks for the fix . It is working much better now, but unfortunately ... .Thread.run(Unknown Source) Regards, Natalia. natmaclin Natalia Levine It indicates that the fix

size is 64KB, but unfortunately somehow this was not enforced by ObjectDB. This was fixed now ... to 64KB by using 64KB if a larger page size is specified. We preferred a soft fix rather than an exception in this immediate fix , and we will consider adding an exception in future versions. support

only for ID classes and not for simple single field IDs. Version 2.2.3_01 should fix this. Thank ... You should use 2.2.3_01 (the fix was applied after the release of 2.2.3). I just added it to the Maven ... to my mvn repo and this fixed the problem. thank you very much for this very quick fix !   btw

indicates using of ObjectDB 2.6.0. The fix was added at 2.6.0_03 (see #4 above). Although the Explorer can handle missing types also before this fix , these missing types are limited to managed ... implements the private OSGi interface CodeArchitectureExt. You have provided a fix in ObjectDB 2.6.0_03

that has already been fixed . The stack trace is produced by ObjectDB 2.3.7, which is 2 years old now, and many issues have been fixed in the last 2 years. Please try switching to the last ObjectDB version ... it to fix the database, if necessary.   support Support We have changed the JAR file to [2.5.3_03

, but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal error was thrown (details here: http://www.objectdb.com/database/issue/285 ), but the fixing went ... to multiple entity objects. support Support Thank You for the fix . We will consider reorganizing our data

Sylvain Thank you for this report. Build 2.6.2_03 should fix this issue. support Support Thx ... the EntityManager) but not that the relationship is activated. The unit tests were also fixed following ... for that ? xirt Sylvain Thank you for this report. Please try build 2.6.2_04 that should fix this issue

. Please try version 2.0.5 that fixes the problem. support Support Thank you for your reactivity.   ... and that don't fix the issue. I try it with the test application and my full application. In both case the bug is still there.   Do you check if the new version fixes the problem on the test

=. Build 2.4.7_17 fixes this behavior. support Support Thanks for the quick fix . This new version 2.4.7_17 fixes this issue. pezifromvienna Peter Sauer

after fixing the relationship on the Document side to:     @OneToMany(mappedBy="document ... of the collection fixed the issue! thank you very much for your great help. farid oudjanef Farid Oudjane ... that should fix it. support Support I will try that. Thanks Farid oudjanef Farid Oudjane

- the information should be used to fix the application. To fix broken references (i.e. to replace broken ... . This cannot replace fixing the application but it is an easy way to repair a specific database. support

fixed an issue with queries ( issue #2858 ) but had a known query performance regression. It was fixed ... that has not been fixed . Changes in versions 2.8.9_03 - 2.8.9_06 are not expected to affect queries. An attempt

cache is fixed and not released by ObjectDB. You can try reducing its size.  Are you sure ... faults and fix them, but the soft references to entity objects behaviour seems normal.   ... that may be created.  I also understand that those PAGs are fixed and ObjectDB will not free them.  I

to fix the DB file, the Doctor deleted all listed instances of TC. Could u please help me clarify ... _05 it might be the critical schema bug ( issue #2621 ) that was fixed in version 2.8.4. Please try ... did not help. We tried to open a DB with already corrupted data (by the schema change, without fixing

Support build 2.7.1_08 does not fix the problem. sjzlondon Steve Zara You are right, sorry. It fixed a simplified test case but not your exact test case. Build 2.7.1_09 should fix your test case as

,   just tried the fixed version. Two notes: 1. For a composite key an instance of the target ... ); // false tsichevski Vladimir Tsichevski Point 2 is indeed a bug. Build 2.4.7_09 fixes ... you for fixing previous problems. Here is a new one. Using the same class structure as in my previous posts

I get when is below - it complains about a casting issue. Let me know how to fix ... that should fix it. support Support Perfect - it is fixed - Thanks a lot - was very quick - I am impressed. EKK Emmanuel Keskes

that way!    mHornbach Michael Hornbach Just verified that the problem is fixed here in Canada too - one or two second response time. Thank you ObjectDB for your quick fix ... a flood of automatic requests (for ObjectDB jar files and for other unrelated jars). As a fix we moved

a partial fix and the following test should work: package com.objectdb.test.bug.forum; import java.io ... the revised test. support Support Build 2.3.4_03 should fix also the type literals problem ... Adam Build 2.3.4_04 should complete the fix of this problem. support Support

order to understand and fix the problem, could you please provide some information about your use ... to have a fix soon. However, please consider replacing CacheableJobAccountingInfo[] with List ... us some help? CacheableDate is Embedded entity. Marta Maruta M Sedlakova Build 2.5.0_06 should fix

Fixed unstable  activation issues. Fixed   issue #2954  - using IS NULL (or == null) on parameters in queries. Fixed automatic schema update on renaming or moving an enum type. Fixed issue #2964  (critical) - concurrent update of large objects with version-check=false.

Fixed bugs in cascading merge and refresh. Fixed an internal  java.lang.ArrayStoreException bug (com.objectdb.o.InvToOneLoadRequest). Fixed a regression bug (starting 2.4.4_13) in handling embeddable types. Fixed a performance regression (since 2.4.4_01) in query result retrieval. Added INFO

Fixed a bug in queries on embedded objects in C/S mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code enhancement in Java EE server. Fixed a bug in multi variable queries.

Added support for using ObjectDB with JBoss AS 6.0 / 6.1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.

Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException  on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue

parts of the project.  Making sure that only one version - 2.7.2_07 - is used seems to have fixed ... since fixing the objectdb dependencies I am happy if this bug is closed. sjzlondon Steve Zara ... again please reopen it and report. support Support Apparently this was a regression caused by fixing issue #2027 . Build 2.7.6_08 should fix it. support Support

Fixed a bug in query execution optimization ( issue #2170 ). Fixed cascading delete through unloaded (lazy) relationships. Fixed a NullPointerException when using "objectdb.temp.page-file" ( issue #2163 ) Added logging and suspend exception for  issue #2153 . Fixed a bug in using SIZE with

to NonTransactionalWrite enabled ( issue #142 ). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in viewing TreeSet and TreeMap in the Explorer. Fixed detachment of entities by replacing proxy objects with ordinary objects. Fixed a schema evolution bug when adding a new super entity class .

hours of my time. Please attend to this as soon as possible and fix this carefully. I look forward to having this fixed and to having a robust ObjectDB working on my problem, as I am greatly encouraged ... Support Setting fetch=FetchType.EAGER on 'ownedElements' does seem to fix it (the lists load non-null

(and to benefit from other fixes you have performed).     webel Dr Darren Kelly I appreciate ... should fix these issues. Thank you for this report. This work is based only on your first post in ... Thanks for the Build 2.6.9_01 fix attempt. I have tested it exhaustively. Both of the test

;    }     support Support Fixing this bug may require totally new implementation of merge operations. So unfortunately an immediate fix is not possible. But this issue has a high priority and hopefully will be fixed soon. support Support This bug can also cause an "Attempt

. - has 142351616 entries instead of 142351618 jastorga Juan Try to run the Doctor to fix the production database. Do you still get the exception in production after fixing the database? support Support In ... in issue #1977  that was fixed now in version 2.7.1. The new version fixes a critical bug

feedback. Fixed a bug in filtering mapped by objects by type. Fixed a regression bug in using primary key fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.

_03 that was fixed in build 2.05_04. I just opened your sample odb file using the Explorer of 2.1.0 ... . Version 2.1.1 fixes this issue. support Support Thanks for the quick fix . Version 2.1.1 fixed the issue.  mithu1408 Md. Towfique Imam

other recent builds, but to issue #1818 , that was already fixed . It is unclear why the previous fix is not ... correct. Thank you for the fix . btc_es BTC EmbeddedSystems

. Is it possible that your application has a similar condition? Build 2.6.1_01 should fix this exception ... should fix this issue. If the exceptions in your application are due to modifying a persistent collection ... ; support Support Thank You. 2.6.1_02 fix our problem. Now come no more errors. btc_es BTC EmbeddedSystems

continue that discussion on that thread. felixobjectdb Richard Szurgot Yes, this should be fixed in one of the next builds. support Support Any idea when this will be fixed ? bensteele Ben Steele No immediate fix is currently planned. The workaround is to make sure that every new (or modified) type

;      int x;     } } Build 2.6.0_04 includes a fix of this issue ... is still not fixed . wua Andreas Wurm You are right, sorry. Somehow the fix has not been integrated

automatic schema evolution of enum fields. Fixed A NullPointException when using EntityManagerFactory with different class loaders. Fixed a missing call to @PostUpdate when object change is detached by  JDOHelper.makeDirty . Fixed opening context menu in the Explorer.

. This requires fixing the application (making sure that references to deleted objects are removed ... , it wouldn't be easy to find and fix it. If you can share your test so we will be able ... , we may be able to understand and fix the issue. support Support Hello, we have another fresh

. Fixed a bug in reflection mode in detecting changes after flush ( issue #1602 ). Fixed a NullPointerException is merging objects of new types . Fixed a bug in managing inverse (mapped by) collections and maps in reflection mode.

- this is the preferred solution (assuming this is indeed the problem). support Support Build 2.3.6_14 fixes ... after retrieving the BeitragVertragArt class, changing some fields and writing it back? The fix in _14 fixes the Explorer only, right? quasado Alexander Adam If you have a problem in retrieval

". Check the database in the Doctor, if it is already corrupted then first fix  it using ... for something else. The ultimate way to find and fix issues is to provide a test case. See instructions ... , however, that if the problem is the sync setting and the move to ext4, changing the setting without fixing

Thank you for this report. Build 2.2.9_01 should fix the deadlock. support Support Build 2.3.7_04 fixes another case of this deadlock that was not covered by the previous fix . support Support

Fixed a bug in lazy loading of instances of non enhanced classes. Fixed a bug in using the Replayer with no updates to the database. Fixed an activation bug.

the new implementation of temporary files for very large transactions. Version 2.6.7 should fix this bug. support Support Version 2.6.7 don't fix the bug:  (Now there are other line Numbers in PAG ... Support Also Version 2.6.7_1 don't fix the bug: Exception in thread "Thread-174" [ObjectDB 2.6.7_01

Markus Ritter Did this happen again after already fixing the database with the ObjectDB Doctor? support ... . New database copy is ready at: db/smartcal.odb. fixed I enabled Recording so next time I will be able ... ) which reproduce the error. Thanks Markus doppelrittberger Markus Ritter Build 2.7.1 should fix this bug

Luc Have you tried 2.4.5 or 2.4.5_03? Because 2.4.5_03 fixes a GlassFish integration issue . support Support This issue will be closed now since it is assumed that the problem was fixed in 2.4.5_03 ... .6 fixes another regression issue with GlassFish, which may be related to this report. support Support

Thank you for this bug report and for the test. Version 2.3.1 fixes the exception. Some performance ... and caught I think) according to my profiler.  Once I fixed my test, the ID lookups are 5x ... fix for this problem (following issue #531 ). support Support