ObjectDB Database Search
101-144 of 144 resultsExplorer in 2.3, threads, query- cache , memory usage, etc...) to use for tuning b. Show all database connections | |
Does ObjectDB create one instance of each entity class on (web app) load ? to the EntityManager metamodel for caching some oft-used information in an application-wide | |
find() cost unreasonable time! @Inheritance(strategy=InheritanceType.JOINED) // Success for Inheritance Sonsection //@ Cache (size=10000 | |
Why the internal error was thrown? cache , but unfortunately it is unclear how this happened. support Support We get this exception | |
OneToMany and cascade delete problem are removed from the cache and then retrieved again, fixing the broken relationship). When using a short | |
objectdb on single server 20TB storage possible ? features: Virtualization: AMD-V Caches (sum of all):   | |
Unexpected behaviour upon update. Bug?); } } nullcrud N J It seems to work as expected. The entity object is cached in the EntityManager as | |
Memory Leak in EntityManagerFactory ? of the profiler. First i thought it might be the L2 Cache or something simular but then i could not understand | |
Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity a cache of loggers keyed to classes for lookup: public final class LoggerWrapper extends | |
Many connections possible? and will it makes problem in future? My questions is about : 1-) Can objectdb server handle 200.000+ connections at the same time concurrently ? Does it have queue and cache ? 2-) is it dangerous to use that system on many online users ? kadirbasol Kadir BASOL Having 200,000 concurrent threads is probably a bad idea. Usually | |
ObjectDB version 2.2 has been released cache bug. Fixed several bugs in query processing and running. It is highly recommended to run | |
Need to close+open database for a commit to be taken into account+reload. Thanks. lo Hoel Maybe you should try disabling all sorts of cache in the configuration file | |
Spring Data JPA. Everything works fine now. Seems that maven had cached some old jar. mosi0815 Ralph Moser | |
performance tuningwe have a customer system with 64 GByte RAM, 16 CPUs on 8 sockets, the fastest possible ssd. we wonder if the cache and other settings can be optimized to get the most performance these are the current settings, please advice what we could optimize hgzpincher Hans-Georg Zwicker | |
Dirty checking itself doesn't alter the database, by rolling it back after I've generated the views. Your caching probably | |
Problem with @Basic(fetch = FetchType.LAZY); //Close everything and reopen to make sure no cache of the description / code is left | |
Multiple inputs not supported on WHERE ? my code block : @CacheEvict("loginsList") @Transactional default int updateUserEnabled(Boolean enabled , Integer sicilNo, Cache loginCache) { Optional bySicilNoOptional = findBySicilNoOptional(sicilNo);   | |
Unexpected exception com.objectdb.o.PAG.N()" because "this.h", it appears this issue is an internal bug related to how cached pages are stored in temporary files | |
updating one to many sometimes fails to another due to CPU caching or the lack of memory synchronization. It is important to remember | |
large numbers of records, but obviously slower than when using a small database that can be cached entirely in memory | |
Wrong select results after odb server restart. Is this some caching problem? mastervoland Vladimir Sadovnikov   | |
config optimizing we have a customer system with 64 GByte RAM, 16 CPUs on 8 sockets, the fastest possible ssd. we wonder if the cache and other settings can be optimized to get the most performance these are the current settings, please advice what we could optimize   | |
Sorting problem). Then it should work. lwalkowski Lukasz Walkowski Yes, and ObjectDB manages a query program cache | |
Remove a modified entity cause an optimistic lock exception). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity | |
Dependency from enhanced classes to the objectDB library: An unrecoverable error occurred. This form was missing from the server cache . Try reloading the page | |
combined index not used of this query fells to 1457 on repeating runs (when cache is disabled), will be checked now | |
Database File Compression ObjectDB database files are usually smaller than database files of other Database Management Systems (object databases and relational databases) but additional internal compression is still possible. Usually smaller files are also faster because less I/O operations are required and memory cache | |
new objects not available in mappedBy associations the object is retrieved again from the database (and not from the persistence context cache ), or | |
Unexpected not reproducable exception in a query BTC EmbeddedSystems The stack trace indicates an unexpected state of the query result cache | |
ObjectDB enhancement fails on "is" form for @Transient boolean isLoaded(), ok for "getter" form @Transient boolean getLoaded(), and on complete clean and build in NetBeans, and also after complete NetBeans cache clear | |
Terracotta Ehcache Integration Hello , it will be good if you make alliance with terra-cotta ehcache. Their distributed memory cache is very fast.IF we mix with your engine. It will be very great for us. kadirbasol Kadir BASOL | |
ObjectDB 2.3.2 instead of Long ) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh. | |
ObjectDB 2.6.9 cache InternalException. Fixed JDO PersistenceManager 's newObjectIdInstance to support classes | |
ObjectDB 2.2.0 class. Fixed a query cache bug. Fixed several bugs in query processing and running. Fixed a query | |
ObjectDB 2.2.7 Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache . Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance | |
Unexpected exception Error 990.getResultList(JpaQuery.java:686) at com.ysoft. cache .objectdb.ObjectCacheDB.search(ObjectCacheDB.java:433 | |
ObjectDB can't be activated activation key. Maybe your activation server is broken? skolb Sebastian Kolb Maybe it is a cache | |
ObjectDB 2.7.0 the first entry (required by Apache Karaf ). Fixed a cache bug in repeating some sorts of LIKE queries | |
ObjectDB 2.8.0;unexpected internal exception in query result cache ( issue #2406 ). | |
query.getResultList() throws ClassCastException+ faster on existent entities. Ok, good to know. I've already looked into enabling level 2 caching | |
Exception makes the system unusable for several minutes it is a cache issue? How does you application response to these exceptions? Does it try refreshing | |
ObjectDB 2.0.0 in preserving order of @EmbeddedId fields. Fixed a NullPointerException during cache cleanup. Fixed | |
javax.jdo.JDONullIdentityException: The identity must not be null.). How is the main db file and the one with $ appended actually playing together? Is it some kind of cache | |
ObjectDB 2.2.2 Changed log format to include date and time . Changed class loader management. Fixed handling multiple order expressions in inverse (mapped by) fields. Fixed the behavior of CacheStoreMode setting in L2 shared cache . Fixed TreeSet and TreeMap element comparison bugs. Fixed an Explorer |