About memory

release

2.4.0

... space. Removed a shutdown hook that leads to memory leak ( issue #63 ). Completed missing documentation ... UPDATE & DELETE queries). Fixed memory leak issues. Fixed server hang and deadlock issues. ...

 
release

2.0.4

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
release

2.0.2

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
forum_thread

Bidirectional OneToMany is slow on updated items

Hello, I have a problem with the following situation. I insert persons with addresses. In the first run, they are all new with a new address. It runs fast. In the second run, the persons are all loaded and got a second address. This seams to be much slower. The Entities are all enhanced by the javaagent (which you can see in the contained eclipse launch configuration) Is there any way to speed it up?       ... calls of Address and Person instances with an in memory HashMap and get calls. ObjectDB Support ...

 
forum_thread

Removing entity class

Hello, I am using evaluation version of ObjectDB for long term private project. Recently I hit the 10 entities limit and got exception: com.objectdb.o.UserException: Too many persistable types (>10) - exceeds evaluation limit Among the 10 entities in the project there are 2 entities I added long time ago and they were never really used. I deleted them from Java source code, but there are still in ObjectDB database. The 2 tables for these entities are empty, but the tables exist, so they count into 10 entities limit. ... to a new database. If the database is larger then memory it may become more difficult. ObjectDB Support ...

 
forum_thread

Multithreading Test and Deadlock

I move on to testing the multi threaded part of ObjectDB. From the same code (MyMain.java), I set the thread count from 1 to 4 and not only do I found it's slower overall (each thread only needs to insert 250K entities) but the threads are stuck with a deadlock. All threads share the same EntityManagerFactory but they have their own EntityManager. The stack trace is attached. ... maybe in this test 4 threads are slower because of higher memory usage (4 x 10,000 x 100 strings x attribute length => many MBs). ...

 
release

2.0.1

... a failed find followed by persist. Fixed a memory leakage in eager load of large object graphs. Fixed a ...

 
forum_thread

multi thread application, id field sporadically null

We are testing objectDB with a multi thread application. Each thread has it's own entityManager created from a common factory. In one thread we receive sometimes an object from the database with the field that is declared as @Id having the value null (what is not correct, we checked that with the explorer). The class is declared like this: ... ... is setting the id. Maybe you retrieve a cached object from memory, which is a new object that has no id yet. You may want to check if ...

 
forum_thread

JDOHelper.isDetached failure ?

Running this example code: ... to support it for non enhanced classes, without causing a memory leak. ObjectDB may be the only JDO implementation that supports ...

 
forum_thread

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

Hi, the following exception occurred in our production machine last night: 2013-07-17 20:41:46,665 pdnsrttor3rc42-WSAgent-2-Existing/16 ERROR ObjectDbMessagePipe - Failed to put a message on queue:  pdnsrttor3rc42-ReportDSGroup_Instance-2 retrying = true [ObjectDB 2.4.6_10] javax.persistence.RollbackException Failed to commit transaction: Java heap space (error 613) We are using ObjectDB 2.4.6_10, JDK 7, and a 30GB heap space. ... the exception mentioned above and instead keep allocating memory until the JVM itself detects an OOME and subsequently terminates the ...