About WRITE

issue

Database access error , Doctor hanging on trying to repair, production shutdown at our biggest customer

we have a database shutdown, logs are showing: [2017-07-10 21:07:23 #1 store] Database 'F:\Hummingbird\Objectdb\db\coreSystemDb.odb' is opened by 11028@wzbhb101 [2017-07-10 21:07:23 #2 server] Server on port 3333 has started by 11028@wzbhb101 [2017-07-14 07:08:38 #3 store] SectionClassifier: SectionClassifier{2->merger[2699]-missing:1} [2017-07-14 07:09:08 #4 store] SectionClassifier: SectionClassifier{2->merger[2699]-missing:1} ... the performance significantly, right ? If you write the recording to a different fast disk then the effect may not be that ...

 
release

2.4.0

... in optimistic locking on find by using LockModeType.WRITE . Fixed exception when a named query doesn't exist ... in criteria queries . Fixed a "Failed to write the value of field property" bug. Fixed a  ...

 
forum_thread

OutofMemory error with Object DB 2.0

Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2.0 The application works with 256MB heap size with objectdb 1.0  But on 2.0 even with max heap size of 1024MB, I get this error. The application reads xml file of around 1GB and creates a new odb file and inserts 200 records at a time. ... sync = "false" path = "." mode = "write" /> <locking version-check = "true" /> ...

 
release

2.4.1

... in optimistic locking on find by using LockModeType.WRITE . Fixed exception when a named query doesn't exist ... in criteria queries . Fixed a "Failed to write the value of field property" bug. Fixed a  ...

 
forum_thread

Replication error - parsing objectdb config

I'm trying to replicate a database using the following config: <server>   <connection port="6136" max="100" />   <data path="$objectdb/db-files" />   <replication url="objectdb://localhost:6126/DEV1/NewMessagePipe.odb;user=admin;password=admin" /> </server> ... "true" sync = "false" path = "." mode = "write" /> Logs from the master and slave are attached but ...

 
release

2.3.7

... in criteria queries . Fixed a "Failed to write the value of field property" bug. Fixed a  ...

 
issue

Internal error

SEVERE: Exception [ObjectDB 2.7.1_01] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.8.0_131 (on Linux 4.13.0-16-generic). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: null com.objectdb.o.InternalException at com.objectdb.o.InternalException.f(InternalException.java:236) at com.objectdb.o.STA.K(STA.java:348) at com.objectdb.o.ENT.F(ENT.java:546) at com.objectdb.o.ENT.O(ENT.java:694) at com.objectdb.o.LDR.G(LDR.java:613) at com.objectdb.o.LDR.F(LDR.java:473) at ... a new build that instead of throwing the exception will write information to the log and proceed (ignoring that unexpected state). ...

 
forum_thread

locks on pure query activities

analyzing the dynamic behavior we can see from the thread dump that a lot of our threads that are just doing simple queries show locks like these (question is: why there are locks and how could we get rid of that):   log1:   ... sync = "false" path = "." mode = "write" /> <locking version-check = "true" /> ...

 
forum_thread

java.lang.NullPointerException when using ORDER BY

We are using ObjectDB 2.5.1_04. The following query causes an internal null pointer exception: SELECT r FROM RecordingMetaData AS r WHERE ((r.mapToCli != '192.168.10.200:9085' AND r.callDirection == 0)) ORDER BY r.startDateTime DESC If we remove the ORDER BY part, the query completes OK and returns the records from the DB, but obviously not in order. Here is the stack trace of the exception: #1 2014-02-20 00:59 We are using ObjectDB 2.5.1_04. The following query causes an internal null pointer exception: SELECT ...

 
forum_thread

500Mb ObjectDb database opening issue

Hi, I have observed that 500 Mb objectDb database opening time is very slow (~3 seconds) for following code m_EntityMgrFactory = Persistence.createEntityManagerFactory( "objectdb:" + aFilename ); m_EntityManager = m_EntityMgrFactory.createEntityManager(); Does exist any way to speed-up open time for big databases? Definitely, it's too long for 500 Mb database! ... <recording enabled="false" sync="false" path="." mode="write" />   <locking version-check="false" />   ... <recording enabled="false" sync="false" path="." mode="write" />   <locking version-check="false" />   ...