ObjectDB Database Search

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

) Is this enough information for someone to suggest what might be happening and how to fix it? public void doEdit() { try ... (it is fixed now). Sorry for the error.  After switching to  setRestoreValues your test works ... to call setRetainValues once per EntityManager.") Yup, my application also works with the fix . The new behavior

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

fixes this issue. support Support Build 2.5.5_01 fixes this issue but it has a new bug. When I ... .5_01. mosi0815 Ralph Moser The new error is not related to the Enhancer fix , but to another fix

Your report shows two different issues. Please try build 2.5.5_04 that includes an attempt to fix them. support Support Thanks for the fix . It helped for the above mistakes, but next one raised 200MB ... the HashMap. Can this be fixed too?  jakab Gergely Jakab This map issue

_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

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

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

/ticket/1823) You had attempted to fix it in build 2.6.6_08. I reported today on investigations by version ... object" when using a TableGenerator. That problem was demonstrated by the provided test case, fixed ... Dr Darren Kelly The bug was found and fixed in build 2.6.9_01. It can affect any application

workaround or could this be fixed ? Is the last (problematic) query invalid from your point of view? Thanks ... this fix /workaround in the test scenario, still trying to establish it in the "real" project. There I ... the queried root entity). I will post a thread there to see if someone can fix it. For so long I

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

, 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

.) java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file1.odb fixed /file1.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file2.odb fixed /file2.odb&\ java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb.Doctor file3.odb fixed

- 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

. 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

to use JPQL keywords as field names. Please try build 2.1.0_01 that should fix it. support Support I did some tests and fix is almost working - there is no more exception with unexpected query token ... but no exception was thrown. Could you upload a test program that reproduces this issue?   Update: Build 2.1.0_03 fixes all these issues. support Support

report and for the test program. Version 2.1.1_01 should fix this issue. support Support Fix works perfectly well. The difference in speed is really huge. Thanks for the fix . lwalkowski Lukasz Walkowski

Version: 2.2.4_04 n0mad Zakaria Yussuf Thank you for this report. Version 2.2.5 should fix this bug. support Support 2.2.5 does fix the issue. Thanks for the quick fix . n0mad Zakaria Yussuf

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

the ObjectDB server doesn't help, try to use the ObjectDB Doctor, first to check the database and then to fix ... understanding and fixing the problem. support Support Hi, I have restarted objectdb server ... , it should be "has 0 entries instead of 280", and it will be fixed ). support Support Thanks for the tip regarding

.java:1055) [09:44:46.992] ... 38 more codefad FrankChu It seems to be issue #621 that was fixed - please switch to build 2.3.6_14. You may have to fix your database file by running the ObjectDB Doctor ... by Doctor. codefad FrankChu Maybe the Doctor cannot fix this specific issue. Try to use 2.3.6_14

temporary file path. Please try build 2.3.7_16 that should fix it. If it doesn't - please try build 2 ... files. Even after a fix , it would be better if possible to avoid temporary file (to improve efficiency ... response !   That fixed it.. Have now split transactions into batches of 1000 recs

without too much pain, assuming recording is enabled from the start. bensteele Ben Steele I managed to fix this by ... that copying the db contents into the data path would fix it as it did the same thing a while ago and that fixed it. I am also finding the recording directories growing upon DB restarts

_02 fixes it. If the problem still exists, please post a modified test case that demonstrates it with the new build.   support Support Thanks for new build. Fix is working correctly. The speed ... a regression bug , so it had to be changed in build 2.4.3_01. Hopefully most of the performance gain will remain also with the new fix . support Support

,   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

=. 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

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.

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

require changing our large existing JDO 1.2 codebase. spiffy Jonathan Harley Build 2.4.7_04 fixes ... classes, should they use the package name? Maybe also the class name? This could be easily fixed if this is how it works in other JDO implementations. support Support Confirmed that 2.4.7_04 fixes

. Stefan Stefan Mair There was a problem with using large objects in the past, but it was fixed ... it seems that you are experiencing a new problem. Apparently progress in fixing this would be possible ... Support This report is similar to the report in issue #1977  that was fixed now in version 2.7.1

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

(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

. - 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

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

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 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.

Fixed an  Explorer bug in handling listeners and callbacks. Fixed a bug in using user/password url arguments multiple times. Fixed several bugs in query processing and running.

Related to #51 that was tested against 2.2.7 and marked as fixed in 2.2.8. Running the same test ... .8_01 that should fix it. If it doesn't work try using enhanced classes (you should use enhanced classes anyway to improve performance). support Support Verified and confirming that 2.2.8_01 fixes the issue. kaosko Kalle Korhonen

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

. Please try build 2.2.9_02 that should fix this. If it doesn't - try to disable the query program cache ... . support Support Any feedback regarding the new build that may fix the memory leak would be appreciated ... ;This issue will be marked now as fixed . Reopen it or create a new issue if necessary. support Support

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

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

it will go away when I fix something in the test itself but I can put one together if the stack trace isn't ... should fix the exception (but notice that the data will not be available and the collection would look ... reference to the containing entity object? support Support Following issue #544  - a better fix

that use ObjectDB. Probably ObjectDB has still some multithreading issues that require fixes . Any test ... Support The stack trace at #2 reflects a bug that was reproduced and fixed using the test in issue #625 . It is possible that this bug caused also the exception at #1 so this issue will be marked as fixed . support Support

- 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

this forum thread ), and was fixed in build 2.4.3_02, but the fix was removed later in build 2.4.3_03 because it caused other problems (#10, #11 in that forum thread ). support Support Version 2.4.4 fixes

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