Internal Website Search

ObjectDB 2.2 has been released and it includes important additions and fixes : Added full support ... after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution

... all work fine.   DB Doctor does not fix the problem. We need guidance on how to debug and fix the problem. Thank you Emil                 prolancer ... RecordingMetaData r For object #1 the id is Integer rather than Long in the second database. You can fix

this without the workaround. support Support ObjectDB version 2.7.0 fixes this issue. Thank you for the report. support Support Thank you for the fix . It works. btc_es BTC EmbeddedSystems Build 2.7.5_07 fixes this issue again after unknown regression. support Support A conflict was found between the fix

we expect that the database will contain 2 B instances at the end of the test. Until that fix 3 B ... .6_17. The fix includes using new entity objects without merging them, which affects your test case ... me if i am wrong, i have just launched your test case with 2.4.5 version ( so before the fix ). Test

move during commit different values can be obtained for the same field. Hopefully a new build that fixes ... should fix this issue. support Support Thank you for making a build that contains the fix available ... all indexes) should fix the corrupted indexes. Also, can we assume that all version prior to 2.6.4_02

ObjectDB 2.1 has been released and it includes important additions and fixes : Added Online Backup ... ( 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

.ClassCastException: com.objectdb.o.PIX cannot be cast to com.objectdb.o. FIX at com.objectdb.o.EIX. (EIX ... (Thread.java:748) Is there any way to fix this? Best regards, Markus Ritter doppelrittberger Markus ... .objectdb.o.PIX cannot be cast to com.objectdb.o. FIX at com.objectdb.o.EIX. (EIX.java:70) at com

.EnumValue is not enhanced.   The " fix ": I discovered that if I include these in the IValue interface the runtime error on attempting to persist disappears (but this does not " fix " the log ... with EnumValue::setOldValue occurs on that attempted persistence.   To " fix " the error include

/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

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

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

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

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

) 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

Build 2.3.4_04 should fix the new "Failed to write to file" error. Thank you for the "mvn ... for the quick investigation. That has indeed fixed that issue. However there appear to be two more. First, as ... the posting instructions may help in providing support and fixing issues more quickly. Thank

Fixed a critical issue that may cause database corruption ( issue #630 ). Initial attempt ... ; toString of criteria queries to use aliases ( issue #12 7). Fixed automatic variable naming in criteria queries ( issue #640 ). Fixed a bug in handling mapped super classes. Fixed bugs in using casting

configuration elements from required to optional. Fixed the "Negative snapshot user count" bug ( issue #556 ). Fixed a page cache purge deadlock ( issue #559 ). Fixed handling ;drop in client-server connection url. Fixed performance issue ( fetch optimization ) in range queries. Fixed cached result size

Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running

and provide a fix . support Support The reason for not using the composite index was found and can be fixed .  As there are too many possible combinations for covering the filter: "a.type = 0 ... combinations to 10000 solves this issue so a quick fix is possible for this specific issue

to collections. Fixed large transaction temporary files implementation ( feature request #1658 ). Fixed a bug in handling large objects with long primary keys as query results ( issue #1717 ). Fixed detachment of embedded objects to collections. Fixed database page objects reuse to release to be cleared

to provide a fix as early as we can next week.   support Support Yes, this is the one that failed ... .5.5_06, which includes an attempt to fix this issue. support Support No its not fixed ... cannot see any new activation by you today. To test the fix please run activation again using the new build

Framework versions (with JPA 1.0). Fixed "InternalException: InterruptedException" due to application interrupts in embedded mode. Fixed a class loading conflict with Log4j. Fixed very slow processing of a composite BETWEEN query. Fixed NullPointerException when using AND TRUE in WHERE clause (issue

.7.4_04. btc_es BTC EmbeddedSystems Build 2.7.4_04 fixes issue #2280  but seems to cause new ... (until commit). Build 2.7.4_04 fixed  it by creating a new snapshot on query execution if changes ... EmbeddedSystems It is possible that the fix in build 2.7.4_04, which improves visibility of committed

. A similar issue was fixed a few years ago and since then this is the first report. First, please check your database with the Doctor. If the error repeats, try to fix the database by running the Doctor ... you very much for this test - it wouldn't be possible to understand and fix the issue without this help

that is already running (avoiding further attempts). Fixed a memory issue with using ObjectDB with JBoss. Fixed query execution issues with using composite indexes. Fixed a bug in using LIKE operator in some combinations of different wildcards. Fixed a bug in handling dates ( TemporalType.DATE

( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed a bug in comparing array fields against parameters in queries ( issue #2289 ). Fixed a bug in retrieving new objects of other transactions after flush ( issue #228 0). Fixed a bug in version 2.7.4 in

of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a  NullPointerExeption on new index building . Fixed a NullPointerExeption on flush ( issue #1840 ). Fixed a bug in using temporary files in

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values ( issue #107 ). Fixed a bug in handling JOIN queries with primary key fields.

ObjectDB 2.3.x to 2.5.2. Corruption of the database that cannot be fixed by the Doctor (due to the  ... .3.x would be a problem because development work I did this year relies on fixes and enhancements ... in the log after that restart, so hopefully the Doctor fixed these index issues. In that case

Fixed an issue with viewing class Ids in the Explorer (see issue #2677 ). Fixed a regression bug (in version 2.8.5) in using AS in JOIN ( issue #2666 ). Fixed a connection pool issue related to memory release ( issue #2663 ). Fixed an Enhancer issue in supporting Java 9 modules and packages

) and either start with a clean database or fix this database by running the Doctor in repair mode (and then verify the fix by using the Doctor in diagnosis mode). Check if your application can bring ... Following your report I could reproduce the exception, I found the bug and fixed the problem. Version 2

the problems with these 2 Person instances without throwing an exception, but fixing these instances ... . support Support Build 2.4.0_02 fixes the Doctor as explained above. support Support I tried the new ... :22) [ObjectDB 2.4.0_02] null lorenz2304 Benjamin Lorenz You are right. The previous fix handled

UnsupportedOperationException  error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed a ClassCastException in using a composite index in queries ( issue #521 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( $objectdb ) in NetBeans RCP

.BooleanValue [null](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Persisted: com.greensoft.entity.value.BooleanValue [64](TEST: A readonly fixed true Boolean value) INFO: RequestBean []: Updated: com.greensoft.entity.value.BooleanValue [64](TEST: A readonly fixed true Boolean value

objects in criteria queries . Improved Explorer performance by disabling EAGER fetch. Fixed critical bugs in using flush. Fixed bugs in cascading merge. Fixed a multithreading deadlock bug . Fixed a bug in using JOIN FETCH with DISTINCT. Fixed Metamodel API's getTypeId  method to support single ID field .

lock free Synchronization ( issue #2327 ). Fixed a regression optimistic lock exception bug (due to fix of issue #2280 ). Fixed a regression bug on remove and persist of an object in the same transaction ( issue #2027 ). Fixed a bug in UPDATE queries that modify more than 10000 objects

database connection details. Fixed unstable activation in Mac OS. Fixed a bug in using FETCH JOIN in criteria queries. Fixed a bug in cascading remove when orphan removal is set. Fixed an IllegalAccessError exception when using abstract non public persistable types. Fixed the result type of a sum query on a single value.

)   btc_es BTC EmbeddedSystems It is unclear how this new issue is related to the fix of issue #2640 ... , so if possible, is is recommended to try fixing the database by running the Doctor. A possible ... was indeed removed.   This is abnormal state for a database, so if possible, is is recommended to try fixing

Changed log format to include date and time . Changed class loader management. Fixed handling multiple order expressions in inverse (mapped by) fields. Fixed the behavior of CacheStoreMode setting in L2 shared cache. Fixed   TreeSet and TreeMap  element comparison bugs. Fixed an Explorer

for very large transactions ( feature request #1658 ). Fixed an online backup bug (no access during backup operation). Fixed JOIN FETCH bugs. Fixed a performance issue with mapped by fetch. Fixed the ObjectDB Maven repository and Maven examples to work with TomEE . Fixed handling merge of an entity with PK == 0 ( issue #1667 ).

This is a continutaion of Issue 61 - unfortunately it doesnt seem that the fix in 2.2.9_03 has fixed the problem. The scenario is still the same: I have two "producer" processes which insert ... themselves!) felixobjectdb Richard Szurgot The fix of issue 61 fixed an important memory leak but unfortunately

Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush ( issue #2640 ). Fixed a StackOverflowError on no access permission to objectdb.conf ( issue #2643 ). Fixed a bug in managing pessimistic locks after using

, but then there should be a recovery file that should be used to fix the database automatically. Did you get this error after a process ... that could could this and has not been fixed yet. If this is the case and your test can cause it - posting the test ... . At least it might be worth trying. support Support Just looked again at the page cache fix (issues

the entity package, this has organization reasons. And I tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not work. We got the same exception as before. I analyzed the bug ... ;And I tested your fix with the last ObjectDB patch 2.7.6_02, but the fix does not work. Changes in

. If I decrease the load, it doesn't happen. If I increase it, I get it very often. Any solution/ fix ... , we will need a sample project (even large and with no source code) in order to reproduce and fix ... - #11 above) have been fixed in build 2.5.5_11. The cause was unexpected order of invocation

activation is found in the configuration ( issue #2817 ). Fixed the error message when required enhancement is missing ( issue #2828 ). Fixed recording of large transactions over 2GB in size ( issue #2834 ). Fixed a bug in executing compound range queries using an index ( issue #2853 ). Fixed a bug

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

to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema evolution (regression of 2.2.0). Fixed a bug in queries on large objects . Fixed a bug in using persistent properties with incomplete enhancement.

? Could you please provide the parameter values for getting the first exception? support Support I could fix ... parameters for testing the first query and if the problem is solved a new build with the fix ... Ralph Moser Please try build 2.3.1_04 that should fix these exceptions. For the following query

. 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