ObjectDB Database Search

at: fixed /./private.odb [./private.odb] Took 20 seconds Filesize before: 495M ./private.odb Filesize after: 489M fixed /./private.odb Could You please advice us what to do ? jakab Gergely Jakab ... upgrade, which might be be fixed by now. It may possibly be solved if you update your entity classes

, that we need in that case delete recording data, and copy fixed file manually also to all slaves? Or is there any simpler way? thamal Tomas Hamal Yes, if you run the Doctor to fix a database, i.e. create a new database file, you will have to start the replication again with a copy of the new ( fixed

Support Thanks a lot - my guess is that 2 will fix it -  Is there a way to know if the temp mrg ... applications for more than 24h and the error is gone with fix 2/ so the fix works for me - Thanks a lot

.6.4_01 includes an attempt to fix this exception. This issue cannot damage the database ... to an older backup seems to help. I will try now the new build of objectDB with the fix . jakab Gergely ... . support Support With the fixed version the application starts again without need to return to backup. So far so good. Thanks! jakab Gergely Jakab

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

the classpath.  This may fix the database. Please check and update. support Support Hello, the work ... was null. But before it was set. Any idea?   Another point: Can we hope for a fix ... that doesn't include field, ObjectDB can delete the value of that field. support Support Thanks, the fix solves the issue btc_es BTC EmbeddedSystems

so satisfied is that there is no roadmap for ObjectDB. We see bug fixes and minor adjustments ... the first years after the release of version 2.0, many critical bugs have been fixed . We are working ... to do that without paying in stability. ObjectDB is an active project, with active support and frequent updates and fixes

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

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

Support Can you provide a bug fix in a new ObjectDB version?   btc_es BTC EmbeddedSystems ... regarding the bug fix ? btc_es BTC EmbeddedSystems Not yet. We will try to provide an update next week ... of the changes introduced to fix another issue ( #2964 , part 2, posts 15+ , where a refresh after a flush

;     } } Version 2.6.8 fixes the bug. support Support The fix solves the issue. But now ... EmbeddedSystems Thanks. Build 2.8.0_01 should fix it. support Support Thanks. The issue is solved with Build 2.8.0_01. btc_es BTC EmbeddedSystems

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

.3_03 (which fixed an issue reported in this thread ). Could you please check version 2.7.3_04 ... id; and that might fix the issue, save memory, and not require database schema change (automatically ... that to see if it fixes my issue.   I am also investigating if my Java 9 module setup needs

.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

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

_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

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

Because of this lock all DB operations were only waiting and we could fix it only via restart of whole application ... them. When a circular lock is found, we should be able to fix the deadlock. If you can verify

an issue (a bug report in the Issue Tracking system)? CBE CBE Build 2.6.8_07 should fix this issue. Thank you for the report. support Support Confirmed.  The fix works for me.  Thanks! CBE CBE

java I assume that if I'll back up the .odb file, delete it and then restore it will fix the issue ... . It looks like the problem is fixed when I close the entityManagerFactory manually (using a dedicated

to run your test. support Support Build 2.2.9_05 includes an attempt to fix the NullPointerException . The fix is based on the stack trace rather than on the test case since running the test project

a persistence.xml file for objectDB fixes the problem. In my case the fix was simple, for all other JPA impl

to the plugin runtime classpath. Fixing   "SELECT p FROM Point p" to  "SELECT p FROM Pilot p ... . It seems that the test works now: support Support Hi Yes it works now thank you. I fixed that obvious bug

_17 should fix this deadlock. support Support could we have some more details as to what has changed ... that was added in build 2.4.4_10 to fix another problem caused the deadlock. All builds pass the same

[Tools Options] dialog box when no database is open. A fix will be available soon in ... build 2.4.0_01 that should fix both issues. support Support thank you for the post, I hava

, because we use inheritance a lot. Is it possible that you can provide a fix ?. We think it must be possible ... if a referenced entity have a reference to another entity) We need a fix that fulfills

of a super class is used by the query program. Version 2.2.9 fixes this bug. Thank you for this report ... an improved fix . support Support Looks like this version works. Thanks, Eitan eitane Eitan Eibschutz

) " fixes " this problem. Only id from both entities cause this exception. Can I somehow check the type ... 2.2.8_01. support Support New version works fine. Thanks for a fix . lwalkowski Lukasz Walkowski

. 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

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.

.Thread.run(Unknown Source) We are currently using version 2.5.1. Could you provide us fix or some ... , you are right. When do you plan to fix this issue? We would like to avoid checking for duplicities in every list of values in our selects:( Thanks Marta Maruta M Sedlakova Build 2.7.2_01 should fix

version 2.8.4 that fixed that issue. support Support I think the schema may changed 2-5 times ... for a database. We don't really know if it is fixed in 2.8.4, as we cannot reproduce in development ... issue related to schema evolution that was fixed in version 2.8.4. support Support

Added support for casting from boolean to int in queries. Changed default value of . Fixed a critical Explorer bug that interferes with queries on enum fields. Fixed a multithreading conflict (missing synchronization) in the JPA metamodel API. Fixed implementation of casting ( as ) in criteria queries.

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

. We will try to find the cause and fix it as soon as possible.   support Support Hopefully we fixed the issue. A new licence key was sent to you, please try activation again with the new licence key.  Sorry for the inconvinience. support Support The problem appears to be fixed . I am able

. Do you have a way to reproduce it? i.e. if we release a build with an attempt to fix ... of the optimistic lock exception and we fixed it in our code. From my sight of view this issue is fixed . btc_es BTC EmbeddedSystems

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

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

a great option. Thanks. RockyMountainMan Brett Banks Thank you for this report. Build 2.6.6_01 fixes ... to the server. support Support Bug fix fully validated. Thanks for the quick fix . RockyMountainMan Brett Banks

on closing a database on a server to 2 seconds(see  issue #2686 ). Fixed a bug in the new option to slow backup in client-server mode (see  feature request #2681 ). Fixed Explorer issue after schema evolution ( issue #2726 ). Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ).

to see it fixed , so Tuple.get would work with any TupleElement, be it Path, Join, Root, or whatever. It would make ObjectDB more conformant to JPA specs, too! ;) Or, if it's not going to be fixed for some ... you for this report and for the test case. Please try ObjectDB version 2.7.4 that should fix

count, but still not completely fixes the issue and I'm not sure how scalable this and costly ... to throttle the throughput.  Now I just have to see if this actually fixes original errors. Trianglehead Json Error This has been confirmed to fix the original problem in production.  Thanks so much again for the unmatched support! Trianglehead Json Error

that this is what happened. At this point there is no path to fix anything as ... numbers. There is no quick solution for updating the IDs as IDs are fixed once set. Fixing

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

A possible deadlock was detected when new types are registered during multithreading activity against ObjectDB. Until this issue is fixed , the recommended workaround is to complete registration ... (); The last command will work when ObjectDB can find managed classes automatically . support Support Version 2.5.1 should fix this issue. support Support

.RandomAccessFile. (Unknown Source) at com.objectdb.o.LFL.D(LFL.java:855) ... 37 more Please provide a fix ... Support Thank you very much for the fast fix . We had directly used the new version. btc_es BTC EmbeddedSystems

another attempt to fix the issue (the chance that this is what will solve the issue is not high ... . Build 2.9.0_02 fixed the original issue by adding a synchronized block, which apparently

on accessing an inverse collection in an entity that has been garbage collected. Build 2.3.2_01 fixes ... Francis Thank you for the test case. Build 2.2.3_05 should fix the problem. support Support

that should fix this bug. support Support Thanks. That fixed the bug. doppelrittberger Markus Ritter

_04 should fix this problem. support Support Thanks - that fixed the test but unfortunately I