About Time

issue

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

The following error is reported for objectdb-2.6.9.jar: Failed to commit transaction: Failed to set numeric value of field property com.greensoft.objectdb.test.entity.Element.id using reflection (error 613) Did not happen with objectdb-2.6.3_04 (which one can easily test and compare in the test console app for NetBeans8.1 provided, as explained below). To reproduce download the app and unpack, open in NetBeans8.1, perform Clean and Build, and Run: ... value-wrapper entity classes. It is going to take me some time to bundle these into a test case and upload it (as these value-wrapper ... (in addition to the post-compile enhancement) have run-time javaagent enhancement on. [Edit: removed run-time javaagent ...

 
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: ... but much more details are needed, it will take a lot of time, and the effort may not succeed. Please check if value size 256 is ...

 
forum_thread

locks on pure query activities

analyzing the dynamic behavior we can see from the thread dump that a lot of our threads that are just doing simple queries show locks like these (question is: why there are locks and how could we get rid of that):   log1:   ... These stack traces show normal waiting for short time locks. Maybe several full thread dumps can show a repeating ...

 
forum_thread

JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception

I'm trying to have the guestbook example running in the following environment: jboss as 7.1.1 final oracle jdk 1.7.0_04 maven 3.0.4 objectdb 2.4.0_04 installed as a module of jboss No IDE is used for building the Guestbook.war only maven.   My GuestDAO code is as follows: ... failure). The version of JBoss was 7.0.x at that time and lots of declaration were also missing in the persistence.xml ...

 
issue

stress test -> com.objectdb.o.InternalException: null

I am running a stress test with 2 users, each making a request to the JSON API (which uses as storage ObjectDB) each 50 milliseconds. An API call might have between 1-4 db calls, but they are relatively light, and the db has just a few MB at the moment. After a few minutes I got this exception. If I decrease the load, it doesn't happen. If I increase it, I get it very often. Any solution/fix? A sample project is very hard, if not impossible, to create, because it uses all the system. ... machine, so the load is very low. In the same time, Tomee stays around 10-20% CPU utilization during the load. ...

 
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: ... and rebuild, which I seemed to have skipped over this time. Thanks for fixing this bug. --- Webel IT ...

 
forum_thread

Unexpected internal exception during set field of an Embeddable to null

Hello, we get an Unexpected internal exception and have no idea what goes wrong. We can reproduce (mostly) the error in a very big use case. In the big use case and we create and persist millions of SignalValueImpl objects (Embeddables). Partly as in the stack trace an Embeddable contain another Embeddable. It seems like that we can't reproduce the problem in smaller use cases with less objects. Stack trace: ... works once on a attched Object and the second time (another attached Object) it results in the error.   ...

 
issue

com.objectdb.o.InternalException: null

After an error in a @PrePersist method in an Entity class, the database stopped working. Fortunately this was in development, but still worrying! The Entity class ... it requires some structural changes that will take some time. Meanwhile, caution is required when updating entity classes, and ...

 
issue

ObjectDB 2 JDO Manual

The new ObjectDB Manual describes how to use ObjectDB 2 with JPA. An additional manual that focuses on using ObjectDB 2 with JDO can help JDO users. But since writing a new manual and then maintaining two similar manuals, one for JPA and the other for JDO requires sufficient effort, this will be done only if there is sufficient demand.  ... to JPA makes me more comfortable in investing valuable time and effort in the ObjectDB product and company as a possible best and ...

 
issue

NullPointer when accessing persistent field

I am afraid this is a large and complex example, and I do not encounter the problem in simple cases, therefore there is no example attached. I appreciate this may make the bug unreproduceable from your end.   ... We have spent some time tracking this down. If we do not do static enhancing we do not get ...