Internal Website Search

.conf <log path="/var/lib/tomcat7/logs/objectdb" max="8mb" stdout="true" stderr ... ">     <log path="/var/lib/tomcat7/logs/objectdb" max="8mb" stdout="true" stderr ... ;log path="/var/lib/tomcat7/logs/objectdb" max="8mb" stdout="true" stderr="true" />  

;server>         <connection port="6136" max="100" />String [] test = new String[2] ;   test[0] = "connection port=6136 max=100" ;max=100 (error 531) Am not sure this is the right place to ask the question

;processing cache="64mb" max-threads="10" synchronized="false" /> ... max-threads we have 16 processor cores and around 400 clients communicating ... ">max-threads="16", but there are no strict rules and tuning for a specific application

think that running the Doctor with 512MB max heap size should be a problem. The Doctor tool ... database. With 512MB max heap size (-Xmx512m) it works ... seconds to rebuild a new database. With 256MB max heap size I got the same 

; String familyName; String address; }     DB1: [firstName=”Max”; familyName ... >     DB2: [name=”Max Mustermann”; address=”26135 Oldenburg”] V2.0: EntityPerson{ String name; String zip; String city;}     DB3: [name=”Max Mustermann”; zip=”26135

ended at '2oq' * Batch ended at MAX * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at '2LG' * Batch ended at '2LG' * Batch ended at '2oq' * Batch ended at MAX If MAX is the last, then it looks like that every thing is ok. 3) An Exception

" sync="false" path="." max="128mb" />     <recording enabled="false" sync="false" path="." mode="write" />     <processing cache="64mb" max-threads

class="pre-java"> <recovery enabled="true" sync="false" path="." max="128mb"/> <recording ... -config"> <recovery enabled="true" sync="true" path="." max="128mb"/>

is to use queries with max results limit. Viewing all the objects of a class without a query and max result limit is not a common feature in database viewers. Any idea

these settings: Page Cache <processing cache="256mb" max-threads="10" /> ... ;processing cache="256mb" max-threads="10" /> > Query Cache: <query-cache results="32mb ... > <processing cache="16mb" max-threads="10" /> Now the behavior is different