8 | Replication failed="64mb" /> <network inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false |
8 | cache optimizing> <general> <temp path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size="50 |
8 | significant performance decrease path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size="50 |
8 | OutofMemory error with Object DB 2.0" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size="50" user="true |
8 | ObjectDb.conf Defaults="64mb" /> --> <!-- error if missing <network inactivity-timeout="0" /> --> <!-- ok if missing <url |
8 | First query takes 4+ minutes to complete> <temp path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size |
8 | How to minimize downtime at clustering.I have run master and slave in 2 different remote servers when master goes off and my app get connecting to slave but it have downtime aprox. 20 sec.How can i minimize this? Manoj Manoj Kumar Maharana The timeout for switching from the master to the slave is currently not configurable |
8 | Exception when dataset bigger than tresholdI was working on reporting service for my application and found a problem with datasets bigger than treshold set in objectdb.conf. <objectdb> <general> <temp path="$temp/ObjectDB" threshold="64mb" /> <network inactivity-timeout="0 |
1 | database corrupt Configuration --> <objectdb> <general> <temp path="$temp" threshold="256mb" /> <network inactivity-timeout="0 |
1 | log entry and massive performance issues when a query that normally takes around 5 seconds was terminated by the timeout that we have set (200 |
