 1 | size (if possible) or tune the ObjectDB configuration. If ObjectDB recovery is enabled then ObjectDB |
1 | with new build 2.5.0_03? The SMMD.org$ is normal (it is the recovery file). More details are required |
1 | without its associated recovery file. However, it is also possible (although extremely rare |
1 | J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting -Dobjectdb.temp.no-resize-clear=true The only other change is that we no longer create recovery or replay files as we were not using these. i have attached our full server strack trace |
1 | " resize="51200kb" page="2kb" />
<recovery enabled="true" sync="false" path="." max="128mb |
1 | : <recovery enabled="true" sync |
1 | OverlappingFileException.rar Apparently there was a problem when a recovery file exists but it is empty. Build |
1 | " />
<recovery enabled="true" sync="false" path="$objectdb/" max="512mb" />
|
1 | for ObjectDB where recovery is possible, something like prevalyer etc. Basically we want to hit a huge |
1 | " resize="500mb" page="2kb" />
<recovery enabled="true" sync="false" path="." max="128mb |