6 | First query takes 4+ minutes to complete> <temp path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size ... ="info" /> </general> <database> <size initial="1024mb" resize="256mb" page="2kb" /> <recovery |
6 | ObjectDB eclipse plugin that is added to my application that currently has 15 eclipse plugins. The size of objectdb.jar is 1.29 MB ( times 15 = 19.35Mb!) - a significant increase in size. With a single eclipse plugin I only objectdb |
6 | large numbers of records system memory. Is this size of database file supported in-memory on ObjectDB. We have a server ... database since version 2.6.4. There is no size limit, but it is a new feature, so if you experience issues let us know. support Support |
6 | Can't get arraylist/vector type attributes the entitymanager I write something like vector.size() or I print it's size or I do anything with the vector |
6 | config optimizing> <general> <temp path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size="50 ... " /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled="true" sync="true |
6 | Wrong data stored in time only fields'})"); List resultList = q.getResultList(); if (resultList.size() > 0) { System.out.println("FAILED records " + resultList.size()); System.out.println |
6 | doctor error message after database getting page errors). The OutOfMemoryError crash when running 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 |
6 | Run out of memory side in C/S mode) 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 |
6 | user defined backup target. 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 |
1 | Large query parameter - out of memory cached query result size. Since Java doesn't provide information on heap memory size of data |
