Internal Website Search

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

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

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

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

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 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

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

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

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

; }     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

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

limiting the number of result objects . If you must support very large query result sets, check the temp ... on your application. Reducing the number working threads in the server can also help. More specific analysis ... ;There is an easy work-around, which is to divide up the deletion into smaller number of objects.  I

entity of the parent entity with entityManager.remove the parent entity still has the wrong number ... ;testRemoveVariant1(). Before the entityManager.refresh call the parent entity has the wrong number of child ... (). Before the entityManger.refresh call the number of child entities is 4 and not 3. This is the reason

files. After conversion I got a slightly smaller file with same number of objects (e.g. 3,3GB old ... . Is the enormous increase of database file size caused by the number of not-embedded objects in ObjectDB 2 opposed ...   JDO annotation ? Yes. 1. Is the enormous increase of database file size caused by the number

JPA Method in javax.persistence.Query int executeUpdate () Execute an update or delete statement. Return: the number of entities updated or deleted Throws: IllegalStateException - if called for a Java Persistence query language SELECT statement or for a criteria query TransactionRequiredException

JPA Method in javax.persistence.TypedQuery TypedQuery setFirstResult (   int startPosition ) Set the position of the first result to retrieve. Parameters: startPosition - position of the first result, numbered from 0 Return: the same query instance Throws: IllegalArgumentException - if the argument is negative Since: JPA 2.0

JPA Method in javax.persistence.criteria.CriteriaBuilder Expression quot (    Number  x,     Expression  y ) Create an expression that returns the quotient of its arguments. Parameters: x - value y - expression Return: quotient Since: JPA 2.0

JPA Annotation Attribute in javax.persistence.SequenceGenerator int allocationSize default 50 (Optional) The amount to increment by when allocating sequence numbers from the sequence. Since: JPA 1.0

JPA Method in javax.persistence.criteria.CriteriaBuilder Expression quot (    Expression  x,     Number  y ) Create an expression that returns the quotient of its arguments. Parameters: x - expression y - value Return: quotient Since: JPA 2.0

JPA Method in javax.persistence.criteria.CriteriaBuilder Predicate le (    Expression  x,     Number  y ) Create a predicate for testing whether the first argument is less than or equal to the second. Parameters: x - expression y - value Return: less-than-or-equal predicate Since: JPA 2.0

JPA Method in javax.persistence.criteria.CriteriaBuilder Predicate lt (    Expression  x,     Number  y ) Create a predicate for testing whether the first argument is less than the second. Parameters: x - expression y - value Return: less-than predicate Since: JPA 2.0

JPA Method in javax.persistence.criteria.CriteriaBuilder Predicate ge (    Expression  x,     Number  y ) Create a predicate for testing whether the first argument is greater than or equal to the second. Parameters: x - expression y - value Return: greater-than-or-equal predicate Since: JPA 2.0

sequence numbers from the sequence. Since: JPA 1.0 String catalog default "" (Optional) The catalog

JPA Method in javax.persistence.criteria.CriteriaBuilder Predicate gt (    Expression  x,     Number  y ) Create a predicate for testing whether the first argument is greater than the second. Parameters: x - expression y - value Return: greater-than predicate Since: JPA 2.0

JPA Annotation Attribute in javax.persistence.TableGenerator int allocationSize default 50 (Optional) The amount to increment by when allocating id numbers from the generator. Since: JPA 1.0

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

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

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

performance). Complex heavy queries with several JOIN operations require examining large number ... ) of the executed query plan (always 1 unless a hint is provided), the total number of query plans in ... (filtering is required because of the huge number of possible query plans). A new version of ObjectDB 2.8.3

and involves many difficulties) we will not be able to support unlimited number of Page instances ... from the heap dump, such as type and number of instances of these byte[] elements in the heap, as ... dump. The screenshots shows a summary in ' number _of_instances' and the paths to these objects from

JDO Method in javax.jdo.spi.StateManager float getFloatField (   PersistenceCapable pc,    int field,    float currentValue ) Return the value for the field. Parameters: pc - the calling PersistenceCapable instance field - the field number

JDO Method in javax.jdo.spi.StateManager long getLongField (   PersistenceCapable pc,    int field,    long currentValue ) Return the value for the field. Parameters: pc - the calling PersistenceCapable instance field - the field number

number currentValue - the current value of the field Return: the new value for the field Since: JDO 1.0

JDO Method in javax.jdo.spi.StateManager byte getByteField (   PersistenceCapable pc,    int field,    byte currentValue ) Return the value for the field. Parameters: pc - the calling PersistenceCapable instance field - the field number

JDO Method in javax.jdo.spi.StateManager char getCharField (   PersistenceCapable pc,    int field,    char currentValue ) Return the value for the field. Parameters: pc - the calling PersistenceCapable instance field - the field number

JDO Enum VersionStrategy java.lang.Object ∟  java.lang.Enum ∟  javax.jdo.annotations.VersionStrategy Enumeration of the version strategy values. Since: JDO 2.1 Enum Constants DATE_TIME Since: JDO 2.1 NONE Since: JDO 2.1 STATE_IMAGE Since: JDO 2.1 UNSPECIFIED Since: JDO 2.1 VERSION_ NUMBER

is of one of the following types, the behavior must be as specified: Number or Character : the parameter

JDO Method in javax.jdo.Query long deletePersistentAll (   Map parameters ) Deletes all the instances of the candidate class that pass the filter. Parameters: parameters - for the query Return: the number of instances of the candidate class that were deleted See Also: deletePersistentAll () Since: JDO 2.0

JDO Method in javax.jdo.Query long deletePersistentAll (   Object... parameters ) Deletes all the instances of the candidate class that pass the filter. Parameters: parameters - for the query Return: the number of instances of the candidate class that were deleted See Also: deletePersistentAll () Since: JDO 2.0

JDO Annotation Attribute in javax.jdo.annotations.FetchPlan int fetchSize default 0 The number of instances of multi-valued fields retrieved by queries. Since: JDO 2.1

in this fetch plan. Since: JDO 2.1 int fetchSize default 0 The number of instances of multi-valued

that number of references from the initial object to be fetched. Parameters: fetchDepth - the depth Return: the FetchPlan Since: JDO 2.0

JDO Method in javax.jdo.spi.PersistenceCapable void jdoReplaceFields (   int[] fieldNumbers ) The owning StateManager uses this method to ask the instance to replace the values of the multiple fields identified by number . Parameters: fieldNumbers - the fields whose values

are to be copied fieldNumbers - the field numbers to be copied into this instance Since: JDO 1.0

JDO Method in javax.jdo.spi.PersistenceCapable void jdoReplaceField (   int fieldNumber ) The owning StateManager uses this method to ask the instance to replace the value of the single field identified by number . Parameters: fieldNumber - the field whose value is to be replaced by

must be as specified: Number or Character : the parameter must be the single field type or

that number of references from the initial object to be fetched. Parameters: fetchDepth - the depth