Internal Website Search

101-110 of 200 resultsRefresh

Query only works correctly when debug printing results

results = query.getResultList(); //Start of debug printing System.out.println("result size: "+results.size()); for(RequirementLevelEntity rle : results) { System.out.println("rle ... : "+reqListIsNull); if(reqList != null) { System.out.println("rle reqList size "+reqList.size

TYPE Expression

;   System.out.println("Size: " + resultList.size());        ... ;   System.out.println("Size: " + resultList.size());       

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

;  <url-history size="50" user="true" password="true" />        ... ;      <size initial="256kb" resize="256kb" page="2kb" />   ... -history size="50" user="true" password="true" />         

Handling "is null" in where clause

; resultList = query.getResultList();     System.out.println("ResultList size = " + resultList.size());     if (resultList.size() == 0) {      ... ;   } } ResultList.size() is always 0. It should be somwhere near 50

Failed to commit transaction: Java heap space (error 613)

> a) What do you suggest to fix the issue above at the root - other than increasing heap size (currently ... size you would have to change the ObjectDB configuration. Relevant parameters include ... side) cache size

Searching lists within objects

, searchResult.size());               ... ; assertEquals(3, searchResult.size());            ... ; assertEquals(1, searchResult.size());             

Ram allocation

increasing the ObjectDB cache sizes in the ObjectDB configuration, as long ... if we have server with 256GB RAM and JVM can use 128GB of that RAM, we can allocate objectDB cache size to 128GB ... Selmanovic Theoretically, the main ObjectDB page cache can use 4TB with the default page size

Doctor - high memory usage

. Optimal setting for this database is about 650MB. It's about ten times of size of database. size should be a problem. The Doctor tool ... database. With 512MB max heap size (-Xmx512m) it works

Empty query results after JAR creation

over the one created by the JAR file my application is working. The Size of both DB files ... the Explorer. > The Size of both DB files is exactly the same There is a default initial database size so you may have the same size for an empty database

java.lang.NullPointerException during access a field, only if the classes enhanced

.IVP.m(IVP.java:155) at com.objectdb.o.IVP.l(IVP.java:137) at com.objectdb.o.ISP.size ... .NullPointerException at com.objectdb.o.ISP.size(ISP.java:175) at com.objectdb.o.CLT.visitRefs(CLT ... .objectdb.o.ISP.size(ISP.java:174) at java.util.HashSet.<init>(Unknown Source) at com.btc.ep