About path

forum_thread

Out of memory

Hi, Today in the middle of the night ODB just crashed leaving this on console screen: ... <general > <temp path = "$temp/ObjectDB" threshold = "64mb" /> ... = "0" /> <log path = "$objectdb/log/" max = "8mb" stdout = "false" stderr ...

 
issue

Use temporary files to enable very large transactions

We have transactions in which many objects are created. These objects are no longer needed in the current transaction after creation. Unfortunately, we will receive an OutOfMemory exception because the objects are kept in the first level cache of ObjectDB. In the forum thread http://www.objectdb.com/database/forum/921 on post #4 you wrote, that ObjectDB should support very large transactions in further version. Can you implement it that ObjectDB used temporary files? ... temporary files in the configuration file . The default path is  $temp/ObjectDB , where $temp is the default Java temporary ... number_of_instances.PNG reference_path_of_byte_array_32.PNG reference_path_of_byte_array_152.PNG ...

 
manual

[ODB1] Chapter 4 - JDO Metadata

Shows how to define JDO metadata for persistence capable classes.... file located in META-INF , WEB-INF or in any other path at the level of the classes or above. Determining where to put the ...

 
forum_thread

Exception when dataset bigger than treshold

I was working on reporting service for my application and found a problem with datasets bigger than treshold set in objectdb.conf.   ... <general> <temp path = "$temp/ObjectDB" threshold = "64mb" / > ... - timeout = "0" / > <log path = "$objectdb/log/" max = "8mb" stdout = "false" ...

 
release

2.5.0

... #48 ). Fixed a bug in compilation of path expressions in queries. Fixed handling null  values in JOIN and path expressions in queries. Fixed a possibly very slow query ...

 
release

2.5.6

... Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a ... #48 ). Fixed a bug in compilation of path expressions in queries. Fixed handling null  values ...

 
forum_thread

High memory consumption even after close() of EntityManagerFactory

Hello, we still have memory usage problems. When debugging, we have now observed a case in which the execution of multiple queries increasingly byte array were generated (about 1.5 GB) which from GC could not be released. Not even after the EntityManagerFactory closed. We created a small test with which you can observe similar behavior. The huge memory usage only occurs if we execute the query (line 56 to 61). If we remove this query, all is well. The memory is only released after we re-run a query (on a different database). ... Addendum: With the configuration <temp path = "$ temp" threshold = "1mb" /> is the byte array only 3MB. I ...

 
release

2.7.2

... on internal errors. Added configuration path writing to log on database opening. Version 2.7.1 ... Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a ...

 
forum_thread

Access objectdb.conf as class loader resource

Hi, is it possible configure ObjectDB so it searches the objectdb.conf file as a class loader resource? Regards, Vladimir ... If a configuration file is not found at the expected path , then it is loaded as a resource from: META - INF / objectdb. ... is included in objectdb.jar as a resource at that path. You may try putting your jar file with your configuration resource before ...

 
release

2.5.5

... Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a ... #48 ). Fixed a bug in compilation of path expressions in queries. Fixed handling null  values ...