About files

forum_thread

Upgrade to 2.4.1_01

Hi, We tried to upgrade from 2.3.7_18 to 2.4.1_01 to pickup some fixes. We discovered that our code no longer works when using 2.4.1_01. We did some probing and found one thing. I have attached the unit test to display this issue. The problem seems to be the annotation at line 266 in the test. In our code for 2.3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER), which is wrong, as Contactdetails is Embeddable, the annotation should be @Embedded. Neither annotation works with 2.4.1_01, with each giving a different error. #1 2012-07-03 05:09 Hi, We tried to upgrade from 2.3.7_18 to 2.4.1_01 to pickup some fixes. We discovered that our code no lo ...

 
issue

Unexpected exception Error 990

Hello, following exception occurs when querying objectdb: Bug Version: 2.5.0 Priority: Normal Status: Duplicate Replies: 5 Type:  Bug ...

 
forum_thread

Fetching Collections Puzzle

I am working on a project where I need to travel through a massive graph of objects. One of the main entity is the Node which is shown below. class Node { Node parent List<Node> children Node rightSibling Node leftSibling int rank } I have the following issues/doubts #1 2011-04-23 23:08 I am working on a project where I need to travel through a massive graph of objects. One of the main entity is th ...

 
issue

ArrayIndexOutOfBounds on showing Tree Window

... from the Schema in ObjectDB Explorer in version 2.6.5_04 I get then the following exception (plenty of them). Bug Version: 1.04 Priority: Normal Status: Fixed Replies: 1 Type:  Bug ...

 
issue

Pessimistic lock timeout - blocks indefinitely

I've attached a simple test which creates an object then kicks off several threads which each try to update the object. I'm using a pessimistic lock with timeout as follows: Bug Version: 2.3.1 Priority: Normal Status: Fixed Replies: 3 Type:  Bug ...

 
issue

Server NPE

I'm getting the following NPE when attempting to persist an object to a server based database: Bug Version: 2.3.3 Priority: Normal Status: Closed Replies: 3 Type:  Bug ...

 
issue

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null

Exception in thread "main" [ObjectDB 2.6.0_04] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64-Bit Server VM 1.7.0_51 (on Windows 7 6.1). Please report this error on http://www.objectdb.com/database/issue/new com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at com.objectdb.o.SEM.c(SEM.java:77) at com.objectdb.o.SEC.g(SEC.java:196) at com.objectdb.o.SEC.c(SEC.java:84) Bug Version: 2.6.1 Priority: Low Status: Active Replies: 1 Type:  Bug ...

 
issue

InternalException caused by OOM: Metaspace

Our java server app using objectDB threw this mistake. Looks like due to OutOfMemory exception, but the app was running with -Xmx12G and before the mistake there was used 1,6G from that heap. Although Metaspace can happen independently on the heap usage I believe. Stacktrace follows: Bug Version: 2.5.5 Priority: Normal Status: Closed Replies: 1 Type:  Bug ...

 
forum_thread

Performance issues on aggregate query

we are using this aggregate query to collect some data: #1 2016-11-09 07:49 we are using this aggregate query to collect some data: select p3.doubleValue,c1.classIdentifier,c1.objec ...

 
forum_thread

Mapped (Inverse) LAZY @OneToMany vs. Unmapped LAZY @OneToMany

In the code example below (also attached) I would like to understand why I am able to print to console a lazy @OneToMany mapped field after a finding entity manager closes. There is a switch DO_VIEW_BEFORE_CLOSE, and when it is true the fields are accessed and output before the finding entity manager closes and as expected both a mapped @OneToMany list and an unmapped @OneToMany list are viewable: a.listA_mapped:[{A}[4]"ownedElement1", {A}[5]"ownedElement2"] a.listB_unmapped:[{B}[2]"b1", {B}[3]"b2"] #1 2012-03-14 01:37 In the code example below (also attached) I would like to understand why I am able to print to console a lazy @On ...