About replication

forum_thread

First query takes 4+ minutes to complete

Hi, we are evaluating ObjectDB 2.5.1_04 in embedded mode hoping to replace SQLite in our application. We observed that in our case it takes on average more than 4 minutes to complete the first SELECT query that we run on the DB which contains about 320,000 records of a single type of object. SQLite in comparison responds within few seconds on average with the same number of records. We hope to receive your recommendation on how to improve this result with this post.   Test System ... = "$objectdb/db" /> <!-- <replication url="objectdb://localhost/test.odb;user=admin;password=admin" ...

 
forum_thread

Connection is closed Caused by: java.io.EOFException

I am getting this exception on a regular basis, after a period of time of repeating the same code execution.  I don't understand why.  I restart the DB server and my code works again for another period of time until same exception is encountered again.  I cannot pin down a pattern e.g. after a certain period of time,  because the time  periods between exceptions are not regular, although frequent.  Any test case  I use will pass most of the time but will fail after an undetermined period. ... path = "$objectdb/db-files" /> <!-- <replication url="objectdb://localhost/test.odb;user=admin;password=admin" ...

 
forum_thread

Query results are not up to date for entities, not primitives

When using the CriteriaBuilder to query, the retrieved list are not refreshed according to the latest updates. But, when using the JPQL Query, the list are refreshed. What is the problem? ... \O bjectDB \d b-files" / > < !-- <replication url = "objectdb://localhost/test.odb;user=XXXXX;password=XXXXX" ...

 
issue

Indexes broken after schema update

I don't want to keep creating these issues but the Exception tells me to :), I started a thread to see if anyone else has encountered this at http://www.objectdb.com/database/forum/484 Bug Version: 1.04 Priority: Normal Status: Active Replies: 7 Type:  Bug ...

 
forum_thread

TYPE Expression

Hi there! Trying to add a simple type expression with the criteria api like in your sample: cb.notEqual(e.type(), cb.literal(Country.class)); results in the error: Caused by: com.objectdb.o.UserException: Attempt to store an instance of a non persistable type java.lang.Class at com.objectdb.o.MSG.d(MSG.java:61) at com.objectdb.o.TYW.writeElement(TYW.java:223) at com.objectdb.o.QRR.l(QRR.java:424) at com.objectdb.o.QRR.g(QRR.java:230) at com.objectdb.o.QRR.b(QRR.java:151) #1 2011-12-06 00:01 Hi there! Trying to add a simple type expression with the criteria api like in your sample: cb. e ...

 
forum_thread

@ElementCollection query returning extra result per element in collection

Hi, #1 2011-07-21 15:09 Hi,   I'm having a hard time narrowing down an issue that only became apparent with in the UI. T ...

 
forum_thread

Open several objectdb databases the same time

We tried to open objectdb databases from application and got following error: ... enabled = "true" /> <!-- <replication url="objectdb://localhost/test.odb;user=admin;password=admin" ...

 
forum_thread

Failed to commit transaction: Attempt to commit a rollback only transaction

Anyone know what this means?? Suddenly cropped up.   Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) #1 2011-05-24 22:22 Anyone know what this means?? Suddenly cropped up. Failed to commit transaction: Attempt to commit ...

 
issue

Blocked by find

I have a container object which wraps an objectdb database. There is a "putIfAbsent(String id, Object obj)" method which is synchronized and attempts to load an object by id using the EntityManager "find" method. If nothing is returned from the db the passed object is persisted to the db. I have 5 threads which use this method. In a run today one of the threads seems to have got stuck somewhere in the find. The thread dump looks like: Bug Version: Priority: High Status: Fixed Replies: 23 Type:  Bug ...

 
forum_thread

Pessimistic Lock Timeouts setting

Hi,   I realise that JPA2 doesn't necessarily define a standard API way for Lock Timeouts. However, there is a standardised query 'hint' that can be setup to make the underlying DB lock a record for a specific time. The hint property is: "javax.persistence.lock.timeout" ... I haven't got an easily distributable test for replication, but It shouldn't take too long to write one up if required. ...