Internal Website Search
121-130 of 200 resultsRefreshObjectDB is opening too many sockets sockets. Currently the ObjectDB Server process has 3895 opened files, and from that number ... .04.5 LTS and after some time it causes following error and the ObjectDB is restarted automatically ... (we are using up to 20), but the socket stays there for longer period of time. java | |
each 1-2 days objects on some objectdb level lock/block each other duplicate (e.g. if there is a current time parameter it cannot work). Anyway, it is unclear ... ;concurrently but there is currently a synchronized block that locks the page for a very short time ... look related, it may be simply the exact timing in which each thread dump was taken. | |
Best practise loading big data Hello, currently we take some effort to improve the overall performance ... dump could help in understanding the issue. support Support The current reading scenario ... >We have scenarios in which we open up to lots of different Db files at the same time, each with own entitiy manager | |
javax.persistence.spi.PersistenceProviderResolverHolder"> Returns the current persistence provider resolver. Returns the current persistence provider resolver. the current persistence provider resolver | |
javax.persistence.NonUniqueResultException the current transaction, if one is active, to be marked for rollback. Throwable object information about the current state of the stack frames for the current thread. Returns: | |
retrieveAll(pcs, useFetchPlan). The fields in the current fetch group must be retrieved, and the implementation might retrieve more fields than the current fetch group. If the useFetchPlan parameter is false, this method behaves ... the current fetch plan are fetched, and other fields might be fetched lazily by the implementation | |
retrieveAll(pcs, useFetchPlan). The fields in the current fetch group must be retrieved, and the implementation might retrieve more fields than the current fetch group. If the useFetchPlan parameter is false, this method ... the current fetch plan are fetched, and other fields might be fetched lazily by the implementation | |
javax.jdo.FetchPlan . Specifies that fields that are not loaded but are in the current fetch plan ... that are loaded but not in the current fetch plan should be unloaded prior to detachment. currently active groups and will not | |
getServerDate() their operations according to a single time source. Implementations use the setting of the server time zone to prepare a Date instance that represents UTC time on the server. | |
jdoGetTransactionalObjectId() the current transaction. If the JDO identity is being changed in the transaction, this method returns the current object id as modified in the current transaction. |