 0 | ." Do we have to wait until index activation is finished before we can start using the database or ... are built in the background starting version 2.6.6, and apparently the last related code change was in ... thread that starts when the database is opened and runs until completion. The name of the thread in |
0 | is about starting the online backup. The manual suggests starting it via the EntityManager with the code
em.createQuery("objectdb backup").getSingleResult(); But how do I start it if I am using ... even the source file ? Probably just the new copy. > But how do I start it if I am using only JDO? Your suggested JDO query should work. jakab |
0 | to one of them, enabled recording and started odb. The dbname.odr folder got created so i think ... and started it. The second server starts complaining instantly with the following Exception:
com ... starting transaction #1. If recording is enabled for an existing database, currently the database |
0 | " sync="false" path="." mode="write" /> Before you start replication again, copy the master database ... , no transactions for now) 3) Start ODB Server on slave. 4) Make changes in application (now ... transactions; slave:ODB was stoped since end of case 1) 2) started slave ODB server [NO EXCEPTIONS! DATA |
0 | the errors mentioned above start to happen, after a short while, I have to restart Tomee ... of all the managed types) from the load test, i.e. start the multithreaded load test with a database ... is started (with the already deployed app), then the load test begins. It seems to be related |
0 | and start over After a while and a lot of queries we get the above exception. Thanks Markus Ritter ... that can demonstrate this corruption, i.e. starts with a valid database and then corrupts it? Hello, I did not ... Tomcat, deploy, start Tomcat). Using this approach it will be impossible for multiple processes |
0 | also works with the fix. The new behavior and your quick fix are greatly appreciated. AlphaOne |
0 | of query execution. Added a new temporary system property ("objectdb.temp.quick-file") to accelerate db |
0 | you for a quick turnaround. I can confirm it fixed using Build 2.2.5_10 longpat |
0 | Hi, Thanks for the quick investigation. That has indeed fixed that issue. However there appear to be two more. First, as we are dealing with maps, the "equals" and "hashcode" methods on the key object have to be overridden, so that "containsKey" and "get" methods work correctly. The issue |
