Internal Website Search

than 300GB. It will fit in system memory.  Is this size of database file supported in ... pure memory database since version 2.6.4. There is no size limit

, if BEFORE closing the entitymanager I write something like vector.size() or I print it's size or I

;       <url-history size="50" user="true" password="true" />   ... ;      <size initial="256kb" resize="256kb" page="2kb" />   

; if (resultList.size() > 0) {             System.out.println("FAILED records " + resultList.size());         

the Doctor is probably due to insufficient heap size. The Doctor seems to run fine with the default JVM heap size on a PC with 16GB RAM. Did a server restart solve the issue? If it did

-timeout="0" /> <url-history size="50" user="true" password="true" /> < ... ;/general> <database> <size initial="256kb" resize="256kb" page="2kb

) still keeps the changes in memory until commit. As a result, the transaction size is limited by the available JVM heap size. Actually to be able to store 1GB of data in a single transaction

. Our server does (minimum) one database-file backup per day and the size may be in between 100 MB to 1GB (without documents) which means the size of the backup directory will increase rapidly. To avoid

;url-history size="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb ... ; <logger name="*" level="info" /> </general> <database> <size initial

> Your test demonstrates a failure of ObjectDB in evaluating cached query result size. Since Java doesn't provide information on heap memory size of data structures - ObjectDB does