7 | creating EntityManager on odb file created on Mac 64bit on Windows 32bit.org$ is normal (it is the recovery file). More details are required in order to understand |
7 | In memory processing for ObjectDB for ObjectDB where recovery is possible, something like prevalyer etc. Basically we want to hit a huge |
7 | in-memory and on-disk support? performance and because ObjectDB uses a single file (you can disable logging, recovery |
7 | internal object DB locking in an embedded multi threaded application" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync |
7 | Crash due to memory problems is to increase the JVM heap size (if possible) or tune the ObjectDB configuration. If ObjectDB recovery |
7 | Replication Issue> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled="false |
7 | Degrading performance overtime" resize="51200kb" page="2kb" /> <recovery enabled="true" sync="false" path="." max="128mb |
7 | The server cannot start in CentOS" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false |
1 | Compatibility Problems Upgrading from 2.6.9_04 to 2.7.6. When a database is closed correctly you should not have an .odb$ (recovery) file |
1 | ObjectDB 2.3.4Added 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 #556). Fixed |
