About client

release

2.2.3

... Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non ...

 
release

2.5.7

... thread ).  Fixed a TomEE - ObjectDB client-server integration issue ( issue #224 ). Fixed a ... Fixed "objectdb activation" query to work properly in client-server mode. Fixed enhancing class files that use INVOKE ...

 
issue

NullpointerException at a normal select

When I run the following code: EntityManager em = getEm(); Customer result = null; try {     logger.debug("Ident: "+ident);     result = em.createQuery("Select c from Customer c where c.identifier=:id", Customer.class).setParameter("id", ident).getSingleResult(); } catch (javax.persistence.NoResultException nre) { } finally {      em.close(); } I get the following error (you can also see the log message containing the String parameter at the top): ... have been found ------------------------- Client version: 2.5.6_02 Server version: 2.5.6_02 ...

 
release

2.2.4

... Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non ...

 
release

2.5.6

... thread ).  Fixed a TomEE - ObjectDB client-server integration issue ( issue #224 ). Fixed a ... Fixed "objectdb activation" query to work properly in client-server mode. Fixed enhancing class files that use INVOKE ...

 
issue

Querying error - java.lang.ClassCastException: com.objectdb.o.STV

I'm getting the ClassCastException below when querying objects. As yet I haven't been able to track down the exact circumstance in which it occurs - saving and querying objects works fine on attempts to recreate - but presumably at some point an object gets saved which objectdb doesn't like. Any pointers as to what is wrong or approaches to investigate further would be much appreciated. ...   In addition, a temporary property on the client side disables the suspected optimization: System. setProperty ...

 
forum_thread

Occasionally slow requests in load testing

We are running load testing against objectdb version 2.3.7_18. The performance is generally OK, however there are quite a few "spikes" in the performance where we are getting a lot of very slow response times from the DB, around 10 - 15 seconds. Looking at the DB server process with AppDynamics we can see that most of the requests get stuck in one of 2 places: com.objectdb.o.PGC:w: line number 232 com.objectdb.o.LFL:U: line number 1068 Please see the attached callgraph examples for full stack trace examples. ... order to limit the impact of this issue is to have a per-client configurable timeout on the client size and ideally also ability to retry.  Kind regards, ...

 
release

2.5.5

... a new index. Fixed a bug in setting SSL client-server connection. Added support for checking activation. ... Fixed using type operator and literals in client server queries ( issue #112 ). Fixed eager fetch ...

 
forum_thread

Roadmap - no progress - any plans - transparency?

Hi! I have been using ObjectDB for some time, and I'm relatively glad about it. What I'm not so satisfied is that there is no road map for ObjectDB. We see bug fixes and minor adjustments, which is great, but there's nothing about the future. We need to know in which direction ObjectDB is heading, and if it's heading anywhere or just staying in this state forever, as I see it. It would be nice to have more transparency about this topic. I know there are feature requests already made, but they seem to be ignored. #1 2014-05-11 19:51 Hi! I have been using ObjectDB for some time, and I'm relatively glad about it. What I'm ...

 
forum_thread

Memory leak with OutOfMemoryError exception

Hi, I'm new to using object databases. Currently I'm experience the following error: ... size by running your application (and ObjectDB Server in client server mode) using the -Xmx flag, or alternatively you will have to ...