 1 | My hosting provider recently had a very brief 'scheduled down time'. After which I was getting objectdb exceptions due to max persistent types in database (> 10). Turns out that hosting provider had migrated machines. Luckily I was able to deal with it quickly. I continue to believe |
1 | Hi we have a problem with queries, database is returning wrong results. These are the queries we run from ObjectDB explorer. Query 1 - SELECT MAX(e.generisaniID) FROM AktImpl e – returns string (from field e.brojAkta) although field generisaniID is of type long. Query 2 - select e.idRecord, e |
1 | about how to get the error. Recovery is enabled max="128mb |
1 | , avg, max, min) that are carried out on all the objects (or the object tuples) in the group. Bellow |
1 | . max="128mb" /> Consider decreasing the maximum size to force updating the database |
1 | ="false" mode:
max="128mb" /> In this mode, commit |
1 | file following section
max="100" />
|
0 | ">
max="10" user-max="10" timeout="300" />
max="10" user-max="10" timeout="300" />
All attributes and sub elements shown in |
0 | before throwing an exception:
System.setProperty("com.objectdb.lock.retry.max", "10 |
