About info

release

2.7.0

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.7.1

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.7.2

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
issue

ArrayIndexOutOfBoundsException on flush

The following exception was thrown when my app attempted to flush an objectdb database: ... the additional stack traces do not provide more info and replaying the recorded transactions fail. I am afraid a test ...

 
release

2.6.9

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.6.8

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.6.5

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.6.6

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
release

2.6.7

... 2.4.4_01) in query result retrieval. Added INFO level logging for indicating server start and stop. Improved ...

 
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: ... will be detected as soon as it is created and related info will be logged. ObjectDB Support ObjectDB - ...