About activator

issue

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

NB: the following issue only happens with ObjectDB, it does not happen with EclipseLink.  Glassfish3.0.1 objectdb-2.2.5_10 JavaEE6 web app The error reports as: javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getWidthPxSideBarLeft Where getWidthPxSideBarLeft() is an annotated getter of an entity ViewConfiguration: Bug Version: 2.2.6 Priority: High Status: Fixed Replies: 9 Type:  Bug ...

 
issue

Unexpected exception (Error 990) on find

I have a huge amount of inserts/updates and after a about 850.000 Entities I got the following error: Bug Version: 1.04 Priority: Normal Status: Fixed Replies: 16 Type:  Bug ...

 
issue

Unexpected error when loading all entity instance

Hi, when going through all entity instance to find orphaned entries we get the exception: Bug Version: 2.7.0 Priority: Critical Status: Fixed Replies: 19 Type:  Bug ...

 
forum_thread

Pre-detach loading: retrieval by navigation not working in if statement

objectdb-2.6.3_04 JDK1.7 VM option at runtime: -javaagent:lib/objectdb.jar Experimental mode: objectdb.temp.no-detach NOT USED #1 2016-02-12 01:19 objectdb-2.6.3_04 JDK1.7 VM option at runtime: -javaagent:lib/objectdb.jar Experimental mode:& ...

 
forum_thread

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation

objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property) The following is a detailed report on investigation of multiple issues that have been mentioned in the following forum postings and issue reports (but please do not visit them from here now, the diagnostics there are now obsolete): - Issue #282 - ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection #1 2016-08-21 09:00 objectdb-2.6.9_02  (with "objectdb.temp.no-enhancement-crc-check" system property) The follow ...

 
issue

NullPointer on query

I'm getting a null pointer when running the following code: TypedQuery<ObjectDbMessagePayload> query = em.createQuery("SELECT m FROM ObjectDbMessagePayload m WHERE m.id = :id", ObjectDbMessagePayload.class); query.setParameter("id", msg.getId()); List<ObjectDbMessagePayload> loaded = query.getResultList(); Stack trace follows: Bug Version: 2.3.6 Priority: Critical Status: Fixed Replies: 10 Type:  Bug ...

 
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 Bug Version: 2.7.2 Priority: Normal Status: Closed Replies: 16 Type:  Bug ...

 
issue

Issue with DISTINCT Select

It is getting more and more frustrating :( We've introduced distinct select instead of regular selection in our code (no changes else) and suddenly receive invalid identifiers in queries exceptions in various queries. Here's the stacktrace: Bug Version: Priority: Normal Status: Closed Replies: 12 Type:  Bug ...

 
issue

Unexpected Exception during commit

I'm testing code that otherwise has been working with a clean database. I have seen several examples of the following exception. It never seems to happen in the same place twice, though. If you can give me a hint as to what would internally cause this, I'll try to reproduce it. Carl   Bug Version: Priority: Normal Status: Fixed Replies: 5 Type:  Bug ...

 
issue

Out of Memory - Slow leak?

This is a continutaion of Issue 61 - unfortunately it doesnt seem that the fix in 2.2.9_03 has fixed the problem. The scenario is still the same: I have two "producer" processes which insert messages into an objectdb "queue" database running with an objectdb server process. I have one "consumer" process which reads messages from the queue database and inserts these into an embedded "normal" objectdb database. This is the process which has generated the OOM exception. Bug Version: 2.2.9 Priority: Normal Status: Fixed Replies: 13 Type:  Bug ...