ObjectDB Database Search

-separated list of file name extensions that can be used for temporary databases, which are typically used in tests. The content of these temporary databases is deleted when you use the drop URL connection

further version. Can you implement it that ObjectDB used temporary files? btc_es BTC EmbeddedSystems ... which this data is written to a temporary file. Even without speed optimizations, but with priority ... EmbeddedSystems Although ObjectDB already uses temporary files for many activities (e.g. processing large query

Keskes ObjectDB deletes its temporary files in 2 ways: Every process deletes its own temporary files ... temporary files of other processes that are not locked (active temporary files are always locked ... a separate class loader) manages its own directory of temporary files, e.g.  /tmp/objectdb

memory allocation (and uses temporary files instead of RAM) when memory usage is high, but it is far ... threshold setting. If you reduce the threshold then ObjectDB will use temporary files instead of RAM more often. Processing complex queries may require using many temporary lists, so unfortunately

you have two options for online backup: If your specify a File instance as the target parameter then a temporary ... when the client and the server are not on the same machine, and the temporary file is essential ... then it is interpreted as the path on the server machine to which to write the backup file and no temporary file

Ralph Moser The exception is thrown because of a problem in reading a temporary file that is used in an update query, but the cause is unclear, and according to your report that specific temporary file ... case, but it works well (also with low temp file threshold and temporary files): import javax

we see at the same customer where we have the huge database problems suddenly any temporary batchquery files appearing in a local folder. Beside the fact that the local folders are not excluded from ... Zwicker Local files are generated in the  temporary directory  when processing exceeds RAM

to a temporary data structure for presentation and then on update retrieves the object again and fills its with the data from the temporary data structure - then updates of other users might be overridden. support Support

? Thank you,   Sandu sandu Alexandru Constantinescu You can set the temporary directory ... .tmpdir" system property, but that will change the temporary directory for the entire JVM, not just for ObjectDB.   support Support

is to try different settings. If you have sufficient RAM but temporary files are used a higher general:temp:threshold value can reduce temporary files usage. The L2 cache does not always help

to place this temporary file used during execution of DB Doctor on a different file ... , have you seen the database file becoming larger successfully? You can change the temporary path in

around could you please try: Adding a new temporary persistent field to your  RequirementBasedTestCaseImpl class and then opening the database with the modified class available in the classpath. Removing that temporary

the database. Alternatively you may try using the undocumented setting of temporary page file

are temporary db files.   joesms Joerg Weishaupt Please try the following: Download the last

to release the lock when a connection is  broken ... in case there's a very temporary break

, it appears this issue is an internal bug related to how cached pages are stored in temporary files

the temporary file threshold , but that may slow performance. To understand the problem better

is, that we need the same logic for temporary users (without storing in DB) and permanent users (stored in

you would have to change the ObjectDB configuration. Relevant parameters include: Temporary file threshold

temporary files. Please verify that the ObjectDB process has permissions to create directories and files

you will have to decrease the following default ObjectDB settings: Temporary data RAM threshold . Page

. Fixed a NullPointerExeption on flush ( issue #1840 ). Fixed a bug in using temporary files in large transactions. Reverts a change in 2.6.6_08 that may cause issue #1839 . Attempt to fix a bug in using temporary files in large transactions.

was fixed in version 2.7.2 ( temporary stack traces in the log will be removed in the next build ... Zwicker The log entries in #28 above are temporary logging of the nested section key workaround

amount of data requires using temporary files and the exception indicates a problem in using these files. Please check this forum thread . Maybe disabling deletion of temporary files could help.   support Support

.g. temporary files, recovery file) to other disks. using replication with multiple servers

Attempt to solve temporary files locking issues on Linux.

entity in the same transaction. Fixed temporary file management for very large transactions ( feature

if it fails. If necessary, add a delay between successive find attempts. This may serve as a temporary

( issue #2794 ). Fixed an enum optimization regression ( issue #2794 ). Fixed a temporary files locking issue on Linux ( issue #2794 ).

Added an option to disable temporary file deletion . Added support of using entity classes with missing dependent types. Added support of composite indexes with components of different lengths . Fixed a bug in reflection mode in detecting changes after flush ( issue #1602 ). Fixed

, a temporary property on the client side disables the suspected optimization: System.setProperty("com

a system property to disable the change in version 2.7.6_01, as a temporary solution, if you think

to do an evaluation and want to store 200 million entities in the database.  I have a temporary key

Added support for integration with WebSphere / Liberty application server. Fixed deletin g large transaction temporary files (in the experimental large transactions feature ). Fixed empty log directory creation when logging is disabled. Fixed a bug in using nested embedded objects. Fixed a query

to collections. Fixed large transaction temporary files implementation ( feature request #1658 ). Fixed a bug in

the new implementation of temporary files for very large transactions. Version 2.6.7 should fix

Extended maximum supported entity object size to nearly 2GB. Added a temporary system property to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same object in one transaction ( issue #2027 ). Fixed objectdb.jar to include META-INF/MANIFEST.MF as

had to be moved from a temporary file to main memory. The exception is not related particularly

that is still open? Suspected configuration: Consider increasing the threshold to avoid using temporary files

with the new temporary   "objectdb.page.circle" system property set to "true" - a page circle

(removed temporary object clearing). Fixed the Explorer to show null values in primitive fields

-Georg Zwicker This is strange, and indeed, if the access issue is temporary

Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException  on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue

search values. As a temporary workaround you can use a query hint to request using

Added support of entity classes with missing implemented interfaces in the Explorer. Added method com.objectdb.Utilities.newTrackable(em, cls) for improved performance. Added a temporary workaround for NullPointerException  on query after flush ( issue #1623 ). Improved title of query result