8 | unable to update table in slave server database" /> <recovery enabled="true" sync="true" path="." max="128mb" /> <recording enabled="true" sync="true" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10 |
8 | Glassfish 3.1.2.1 and ObjectDB 2.4.3-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread-queue-capacity 2147483647 ... EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread |
8 | Activation Issue="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10 |
8 | Explorer in 2.3 if you have millions of objects. Currently the workaround 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 |
8 | internal object DB locking in an embedded multi threaded application" /> <recovery enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync ... " max-threads="10" /> <query-cache results="32mb" programs="500" /> <extensions drop="temp,tmp |
8 | How Should I Configure objectdb.conf to Obtain 256KB Disk IO Requests and Maximize Shared PersistenceManager Entity Cache? on an Amazon EBS disk which has max performance at that size and reduces monetary fees by having ... packet requests to the datastore file (because it is stored on an Amazon EBS disk which has max |
8 | Iterating over large result set. Finally, the paging loop could be more efficient in some cases if instead of specifying first/max ... of specifying first/max results you will add a constraint in each iteration based on the ID (primary key |
1 | Service terminated silently (crashed?)...is there any way to cause a crash dump? you should increase the value in the server configuration, e.g. <server> <connection port="6136" max ... and max="0" (which is the default starting 2.6.5) indicates no limit. support Support |
1 | A bug in the JDOQL processor in recent versions of ObjectDBThere seems to be a bug in the JDOQL processor in recent versions of ObjectDB. I've uploaded a "laptop" example to demonstrate the problem. The query in Test1.main should return "ThinkMachine MAX SX ... ) correctly return "ThinkMachine MAX SX 20". Regards. kk8yukawa Keitaro Yukawa Thank you for this report |
1 | Threaded Test - Failed to commit transaction: Unexpected internal exception of each put or take so I wouldve thought the max data I'm holding should be around 20mb (5 consumers * 5 producers * 2mb) and when the consumers alone are running this should drop to a max |
