About fix

71-80 of 200Refresh
Forum
1

Failed to read DB file while online backup is running

you for this report. We found something that may cause this issue, and build 2.6.2_05 should fix ... with the previous fix.   Stacktrace 1: pos = 4107765760 length = 2048 Failed to read from file '/path ... ().createEntityManager(); }     Apparently an attempt to fix the issue in build 2.6.2_05 made it worst
Issue
1

Negative snapshot user count exception

that cannot be fixed by the Doctor (due to the OutOfMemoryError, the upgrade, or any other cause ... on fixes and enhancements you implemented in the interim. I will get you a link to the database ... the log after that restart, so hopefully the Doctor fixed these index issues. In that case
Issue
1

NullPointer on query

while it was writing to the file, but then there should be a recovery file that should be used to fix the database ... is that there is another bug in page management that could could this and has not been fixed ... looked again at the page cache fix (issues #116, #119, #121) and apparently the fix is incomplete
Forum
1

ObjectDB version 2.1 has been released

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

Out of Memory - Slow leak?

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 messages ... me know if you need any further information (except the dumps themselves!) The fix of issue 61
Issue
1

Querying error - java.lang.ClassCastException: com.objectdb.o.STV

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 the database ... the bug and fixed the problem. Version 2.2.0 that was just released includes the fix. This bug
Forum
1

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

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 enhancement report problem ... occurs on that attempted persistence.   To "fix" the error include the operations in IValue   public
Issue
1

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

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

ObjectDB version 2.7.6

mode (no enhancement) by minimising  tracking backups. 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 (issue
Forum
1

"Attempt to lock a non entity object" error

) Is this enough information for someone to suggest what might be happening and how to fix it? public void doEdit ... above setRestoreValues was replaced with setRetainValues (it is fixed now). Sorry for the error ... also works with the fix. The new behavior and your quick fix are greatly appreciated. AlphaOne