Home » Search

About recovery

31-40 of 73Refresh
Forum
2

OutOfMemoryError on search after update on DB created with DB Doctor

It looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenario that results in the OutOfMemory exception problem (using Object DB 2.5.4_04): 1 ... DB Doctor in recovery mode to generate a recovered DB file. No schema (and index) changes - just
Forum
2

Replication issue, Replayer failing due to NullPointerException.

> <recovery enabled="true" sync="false" path="." max ... > <recovery enabled="true" sync="false
Result
2

ObjectDB version 2.7.5

Version 2.7.5 Improved recovery from failure when recovery is enabled with no sync  (issue #2293, issue #2294). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading (issue #2299). Fixed a bug in restricting server access to a range of IPs (issue
Result
1

ObjectDB version 2.0.0

.user". Fixed a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in
Result
1

ObjectDB version 2.2.0

cleanup and reusing space after index deletion. Changed default configuration (enabled recovery
Result
1

ObjectDB version 2.3.4

Version 2.3.4 Added OSGi support. Added support of MEMBER OF for inverse (mapped by) collections. Changed logging of incomplete recovery records from WARNING to TRACE  (issue #565). Changed main configuration elements from required to optional. Fixed the "Negative snapshot user count" bug (issue
Result
1

ObjectDB version 2.5.0

. Improved closing database time when recovery is disabled. Fixed hasSingleIdAttribute for partial primary
Forum
1

Activation Issue

of objectdb.conf: <recovery enabled
Forum
1

Connection is closed Caused by: java.io.EOFException

" resize="256kb" page="2kb" /> <recovery enabled="true" sync="false" path="." max="128mb
Forum
1

Crash due to memory problems

size (if possible) or tune the ObjectDB configuration. If ObjectDB recovery is enabled then ObjectDB