About path

forum_thread

Doctor - high memory usage

Hi, Is it possible to reduce Doctor memory usage? Right now for recovering 67MB database, I need to set heap space to at least 450MB. Even then whole process takes ages. Optimal setting for this database is about 650MB. It's about ten times of size of database. ... the temp threshold from 64MB to 8MB: <temp path = "$temp/ObjectDB" threshold = "8mb" /> then it ...

 
issue

File lock exception on odb$

Not sure if this is an objectdb issue or not but I thought I'd raise it just in case. We had a server failure which caused an unexpected reboot. As a result, the application services which use objectdb were not shutdown properly which in turn meant we had several odb$ files left behind. I had assumed that objectdb would reprocess these when the services restarted but instead we got the exception below. ...   the path in persistence.xml is : <property ...

 
release

2.2.7

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...

 
release

2.2.8

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...

 
forum_thread

Pre-detach loading: retrieval by navigation not working in if statement

objectdb-2.6.3_04 JDK1.7 VM option at runtime: -javaagent:lib/objectdb.jar Experimental mode: objectdb.temp.no-detach NOT USED ...  to files: -Dobjectdb.code.output= <path-on-your-disk> ObjectDB Support ... to files: -Dobjectdb.code.output=<path-on-your-disk> I tried this as a VM option (along ... instead of a system property you can now set the output path in the configuration (objectdb.conf that is available to the the ...

 
release

2.2.6

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...

 
issue

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 into an objectdb "queue" database running with an objectdb server process. I have one "consumer" process which reads messages from the queue database and inserts these into an embedded "normal" objectdb database. This is the process which has generated the OOM exception. ... about who holds most of these instances (i.e. a path to the root) may help. ObjectDB Support ...

 
release

2.2.4

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...

 
release

2.2.5

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...

 
release

2.2.3

... mode. Fixed a bug in setting log directory path (missing URL decoding). Fixed a bug in automatic byte code ...