ObjectDB Database Search

we can see that most of the requests get stuck in one of 2 places: com.objectdb.o.PGC:w: line number 232 com.objectdb.o.LFL:U: line number 1068 Please see the attached callgraph examples for full stack ... The first stack trace (com.objectdb.o.LFL:U: line number 1068 ) indicates massive access

are found with field type GOOD. There are 2 ways generate the bug: Immediately after a new number ... number is printed. There is a 1 minute delay set. The same as 1, but keep ObjectDB's connection open. In this case rerunning the project many times doesn't help at all. Problem: the number of entities

my application and I want to add a person with the same national number as a person already in the database ... with the same national number as a person I want to add. However when I change the value of the national number in the database explorer when the program is running and I want to recreate the person, he keeps

tree with all the instances of a specific class. This is because numbering all the instances ... the maximum number of records 'N' (default to some small number like 10) to display ... , but they may contain collections (explicit or derived) with a large number of elements. Again, most likely I'm

number ;   Which is a part of Customer object: @MappedSuperclass @NamedQueries({     ... (PhoneNumber number ){     principal = number ; }   And making a query: Customer customer ...         number | long | 4567890   Then I'm constructing exactly

the ObjectDB Server process has 3895 opened files, and from that number  3823 are opened sockets ... (firstdb and seconddb) and on the end of the line I wrote number of sockets, which ObjectDB Server ... . Number of opened sockets during the time: Thu Apr 15 15:11:01 CEST 2021 : 0 Thu Apr 15 19:03:01

, float) [2]     7  return       Line numbers :         ... .UNM$f [3]     4  areturn       Line numbers :         ... ;   Line numbers :         [pc: 0, line: 77]         [pc: 10

. The number 36 indicates type version number 36 (i.e. after 35 modification of some entity type). You have an object with that type version number but the type version doesn't exist in the database ... client may send its own version of the entity class to the server, the version numbers are increased

a version number for every entity object, which is increased on every update. An  OptimisticLockException  is thrown when that version number indicates a concurrent update by another user (using ... to the entity class, so the version number will be injected to that field. Please check this version number

this: "com.btc.ep.*, while the new one will be "ep.*", where "*" can be any number of "sub"-packages ... , will there be any limit to the number of packages that we can specify? Will the number impact performance ... ;will there be any limit to the number of packages that we can specify? No. Will the number impact performance

don't have the numbers with me, but I can post what we discovered using different processing cache ... , we are working with an 8-core processor.  The recommended thread count is "more than the number of cores but not too many."  What would be an appropriate number of threads for the processing

stops once a day with no apperent reason. Second cause we suspect is the number of network connections ... , it could be the result of exceeding the maximum number of connections, maybe because new ... is that JBOSS is not on the same server as ObjectDB. After we increased heap size and number

based on the number of search terms. For example, for two search terms: TypedQuery query = em ... there is one index, implemented using one BTree, for the entire database. The number of entries in this BTree may be much larger than the number of Page instances in the database, because each Page

is executed by a ThreadPoolExecuter and the result is stored in ObjectDB. Due to huge number ... and adaptor, pessimistic lock is used. Is this exception due to the limited number of supported thread by ObjectDB? (The default number of supported threads in ObjectDB configuration file is 10

nodes2 derives from nodes1, the type nodes1 derives from nodes. Whether the number is random may be not ... ? Notice that your code uses random numbers to populate the database, so different runs are expected to generate different results. If you can post a simple but complete program with no random numbers

; }     return setOfOtherEntities;   } Now consider a number of OtherEntities ... well, so, the TreeSet is reduced in size? Or do I end up having a number of null pointers in the Sets?  ... could it potentially lead to a number of different exceptions, depending on state, query type

if you provide the exact build number that you use (or upload the ObjectDB jar file). support Support Please find the attached object db jar. binitbhaskar Binit Bhaskar I couldn't find the build number ... number of the odbee jar which is being used is 2302 .  Regards, Binit Bhaskar binitbhaskar

stringValue; } The number of MyStep elements can reach over a million, the number of MyValue objects ... . One is to stupidly commit the transaction after a certain number of read accesses (every 10000 read access ... ;this operation or at least useful information about the number of instances in the heap per type

at a customer the unique object id of one class changed dramatically from a nurmal number to an incredible number which, for sure, cannot be used any more, see screenshot the database is available ... of the entity classes jumped unexpectedly. Therefore, although the numbers are very large and strange

details about the number and types of transactions per minute when the system is on load?   ... ), details about activity ( number of concurrent users, queries by type per minute, new objects ... the number of concurrent threads works better. How do you know that the system is near to collapse

following issue #2379 , as the number of combinations examined by the query planner was increased. Unfortunately, although increasing the number of query plans that are examined can usually help in finding ... . Decreasing the  number of query plans can solve the performance issue in this specific case

. For a number of different List fields, a query performed immediately after creating and persisting ... ][project=TEST: project 1][id=47][name=deep integer quantity ( number of rooms)], [class=BooleanValue ... : project 1][id=47][name=deep integer quantity ( number of rooms)]) INFO: ConfigBean []: testQuery

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field newValue - the proposed new value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

PersistenceCapable instance field - the field number currentValue - the current value of the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager boolean replacingBooleanField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager char replacingCharField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager byte replacingByteField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager short replacingShortField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager int replacingIntField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager long replacingLongField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager float replacingFloatField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager double replacingDoubleField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager String replacingStringField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager Object replacingObjectField (   PersistenceCapable pc,    int field ) The replacement value of the field in the calling instance. Parameters: pc - the calling PersistenceCapable instance field - the field number Return: the new value for the field Since: JDO 1.0