ObjectDB Database Search
151-200 of 200 resultsOutofMemory error with Object DB 2.0 Hi, I am getting the below OutOfMemoryError after I have migrated from objectdb 1.0 to 2 .0 The application works fine with only 256MB heap size with objectdb 1.0 But on 2 .0 even with max heap ... PersistentManager is used to begin the transaction. With objectdb 2 .x do we need to close the  | |
Explorer in 2.3. Then allow import of that file into another database. 2 . Lazy loading of data, especially in table view ... evaluation. For me, #1, # 2 and #3 would be the most important. Also, I've found some small bugs: 1 ... 'recent connections'. 2 . When editing a field in an @Embedded object, I get an error message | |
Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity a non-static logging variable holder can be used in an @Entity. ObjectDB 2 .6.3_04 Apache Log4j2 - 2 .5 Mac OS X   ... ): [ObjectDB 2 .6.3_04] Failed to process class file of type 'com.example.SubEntity' (error 422) com.objectdb.o | |
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 ... our code for 2 .3.7_18, we had @OneToOne(cascade=CascadeType.ALL, fetch=FetchType.EAGER | |
UserException - Object User#2 belongs to another EntityManager Hi! Scenario's steps: 1. User goes to his profile, a JSF page. 2 . @RequestScoped CDI bean ... .pingushare.entity.p1.User# 2 ' belongs to another EntityManager at com.objectdb.o.MSG.d(MSG.java:61) Why does this error happen, because there 2 independent transactions? I guess | |
Closed EntityManagerFactory after upgrading glassfish 3.1.1 to 3.1.2 Hi. I have faced a very serious issue. After upgrading the GlassFish server from 3.1.1 to 3.1. 2 ... more It seems that there is something wrong with persistent context. it seems that glassfish 3.1. 2 behaves differently. I ... to persistent unit lazily. however, glassfish 3.1. 2 immediately after deployment of application logins | |
ObjectDB internal error on 2.6.4.b10 for query with DISTINCT I observed that on new ObjectDb v. 2 .6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $ 2 JOIN $ 2 .values $1 WHERE ($ 2 .namespace == 'com.anritsu.pa3.ttcn3' AND $ 2 .key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2 .6.1.b06 | |
ObectDb 2.3.6 in OSGi environment use a persistence.xml! The stacktrace looks like this: [ObjectDB 2 .3.6] javax.persistence ... .runners.ParentRunner$ 2 .evaluate(ParentRunner.java:222) at org.junit.internal.runners.statements ... ) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$ 2 | |
Another behavior of transaction isolation level in comparing to 2.8.7 I executed the following example with ObjectDB 2 .8.7 a few years ago, it worked. But with ObjectDB 2 .9.5_01 it does not work anymore. It works only, if I uncomment the commit() and begin() in ... (); assertTrue(secondQueryResult.size() == 2 ); assertTrue(secondQueryResult.get(0).strValue != null | |
Embedded in JDO metadata not working in objectDB 2.x ? are embedded too. I did not change the metadata when I was moving from ObjectDB 1 to 2 , I ... . Is the enormous increase of database file size caused by the number of not-embedded objects in ObjectDB 2 opposed to embedded ones in objectDB 1 ? 2 . Could be that ObjectDB 2 is ignoring the "embedded=true | |
Reading 1.x odb files in ObjectDB 2.x without upgrading db odb file from version 1.x to 2 .x, user is unable to open the odb files in the application which is having object db 1.x installed. Is there any way to read odb files from 1.x in object db 2 .x ... binitbhaskar Binit Bhaskar Old ObjectDB 1.x databases cannot be opened directly by ObjectDB 2 .x | |
2.5.3_02: java.lang.UnsupportedOperationException Hello! I use Glassfish 4.0.0 and ObjectDB 2 .5.3_02. When I do entityManager.createQuery I ... Glassfish 4.0 is based on JPA 2 .1. Build 2 .5.3_02 of ObjectDB added initial dummy implementation of the new JPA 2 .1 methods, but the new methods were implemented as throwing  | |
Configuration and Activation Code in ObjectDB 2.x Hi, I would like to update the ObjectDB from 1.0 to 2 .3.7_25. I used the License key ... which i got after acting the 2 .0 odbee.jar. and any specific changes which i need to take care of when upgrading from 1.x to 2 .x. Thanks & regards, Binit Bhaskar binitbhaskar Binit Bhaskar | |
Level 2 cache not hit in @ManyToOne Hi! I have 2 entities: User and Item, both @Cacheable. Item has @ManyToOne private User user. Level 2 JPA cache is activated and it works ok for find by id (tested by changing data in explorer ... performance hit. Problem 2 : executing a query that returns User with id 5,6,7 (or any other) takes fresh data | |
Connection performace after upgrade to objectdb 2 Hi, I have performance problems with objectdb 2 when I tried to get the PersistenceManagerFactory ... only 3ms and PersistenceManager pm = pmf.getPersistenceManager(); takes 40ms However, with objectdb 2 ... . Could you please help me to understand what is wrong with that ? Attached the two odb file for version 1 and 2 . ps. I | |
Upgrade to 2.4.1_03 Right, that fix to 2 .4.1_02 got us past the previous issue. Now I'm not sure ... is: [ObjectDB 2 .4.1_03] javax.persistence.PersistenceException Failed to clear field property com ... .ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$ 2 .evaluate(ParentRunner | |
Issue with merge in 2.4.3 Hi, we just tried to upgrade to 2 .4.3 from 2 .4. 2 . One of our regression tests is failing. Appears objects are getting created twice on merge. Please see attached unit test. Thanks Paul. pedwards Paul Edwards This regression bug was the result of a bad optimization that is now fixed in build 2 .4.3_01. support Support | |
Upgrade to 2.4.1_02 Hi there, The upgrade to 2 .4.1_02 fixed the initial problem ... Sorry forgot the stack trace: [ObjectDB 2 .4.1_02] javax.persistence.PersistenceException Failed ... .ParentRunner$ 2 .evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236 | |
ID format in objectdb 2.x for JDOHelper.getObjectId Hi, I am trying to upgrade the objectdb from 1.x to 2 .x. I installed and configured as per object ... for the same object in object db 2 .x, i am getting Object obj = JDOHelper.getObjectId(logTestRunImpl) obj ... .x to 2 .x. And how can i just get the object id without type id. Thanks, Binit binitbhaskar Binit | |
ObjectDB 2 has been released and is now more affordable Today, after years of hard work, ObjectDB 2 .0 was released and is available for download. In ... of the Server, Site and OEM licenses were sharply reduced. ObjectDB 2 .0 licenses will now include free updates for all 2 .x versions. Private priority support will be sold separately in order to make ObjectDB | |
Activation fails on version 2.9.5_01 Hi, 2 .9.5_01 is rejecting our activation key, and running Activator in 2 .9.5_01 to get a new key ... , both keys got rejected on the respective machines. We have a Site license that should cover all 2 .x releases. Generating a new activation key from the version we currently use ( 2 .8.9.b04) on my work | |
Source not found error after downloading ObjectDB 2.3.7_04 for File PMF.class. I had added the zip file jdo_ 2 . 2 .zip as source. Please help need to complete assg in 2 days Pallavi pallavi You have to provide more details. What kind of error is it? Compilation | |
deadlock with newest version 2.4.4_16 J visual vm is complaining of deadlock since upgrading to the 2 .4.4_16 from _06 and using setting ... . if you could advise that would be great. Dan dansmith Daniel Smith Thank you for this report. Build 2 .4.4 ... that was added in build 2 .4.4_10 to fix another problem caused the deadlock. All builds pass the same | |
A few entities loss after update to 2.3.7_08! The old database is created by 2 .3.6. And recreate the database by doctor is useless. But the other version such as 2 .3.7 works fine. So we believe 2 .3.7_08 has a bug. codefad FrankChu More details are required in order to understand the problem. support Support | |
ObjectDB 2.x is working without any activation code. Put the activation code in the objectdb.conf file and again put this conf file in the objectdb.jar 2 . Used other machine (other developers machine) 2 . Enhannced all the persistance class using this jar file 3 ... .o._JdoDataStoreException: Too many persistable types (10) - exceeds evaluation limit [ObjectDB 2 .3.7 | |
Is 2 level cache in use? Hi, Is there any way to check, if 2 level cache is in use? Right now I've done two things: 1. objectdb.conf with cache size is placed in WEB-INF directory of my web application. 2 . persistence.xml was modified with: But after few benchmarks I don't really see any difference in performance. ODB | |
Internal exception in objectdb-2.4.4_17.jar the same object db. Due to pending releases we have backed out to objectdb- 2 .4.4_06 for now ... . If build 2 .4.4_06 works well that you should use it for now. If the problem is not found and fixed | |
ObjectDB version 2.3 has been released ObjectDB 2 .3 has been released and it includes important additions and fixes: Added the ability to edit databases in the Explorer ( issue # 2 ). Added the ability to execute queries in the Explorer (issue #3 ). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added | |
Is persistence version 2.1 supported?. freddieFishCake Jonathan Lister Thank you for this report. Support of JPA 2 .1 format for persistence.xml was added in build 2 .5.7_05. The url to java.sun.com doesn't exist, so the correct | |
2.4.7 Fetch am noticing in 2 .4.7 that 'fetch' cannot be added to objectdb.conf so, wondering how to enable 'eager' fetching of collections ? Dave dmoshal David Moshal The question is unclear. Is it something new or different in version 2 .4.7? Eager fetching has always been set by annotations or | |
[ObjectDB 2.3.7_25] Unexpected exception (Error 990) copy... [ObjectDB 2 .3.7_25] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64 ... :163) at com.objectdb.Doctor.main(Doctor.java:22) [ObjectDB 2 .3.7_25] null lorenz2304 Benjamin Lorenz There is a problem with 2 Person instances, apparently in their salt byte[] array | |
DISTINCT key causing internal exception on 2.6.4.b10 I observed that on new ObjectDb v. 2 .6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $ 2 JOIN $ 2 .values $1 WHERE ($ 2 .namespace == 'com.anritsu.pa3.ttcn3' AND $ 2 .key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2 .6.1.b06 Harman | |
[ObjectDB 2.5.6_05] Unexpected exception (Error 990) server] [ObjectDB 2 .5.6_05] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_25 (on Windows 2003 5. 2 ). Please report this error on http://www.objectdb.com ... .java:145) at com.objectdb.o.TSK.f(TSK.java:95) [2014-08-24 02:49:35 #34 server] [ObjectDB 2 .5.6_05 | |
[ObjectDB 2.6.9] Unexpected exception (Error 990) [2017-03-29 14:04:44 #1 client] [ObjectDB 2 .6.9] Unexpected exception (Error 990) Generated ... problem.. version 2 .5.6_05 - size of data 100GB I am running a Doctor in prod (in a backup file, It takes long time...), . PRODUCTION [2017-03-30 07:04:53 #37 server] [ObjectDB 2 .5.6_05] Unexpected | |
New issues with queries using build 2.7.6_08 Unfortunately Build 2 .7.6_08 caused exceptions in a lot of system tests of our test suite which still ran successfully with Build 2 .7.6_07. 1. For example following query returns 3 verdict objects ... AND execution.execRecordID = record.uid AND record.executionConfig = config AND config.uid = '23A' 2 | |
[ObjectDB 2.5.1_05] Unexpected exception (Error 990) I have this error in log. The query can't return result. Thanks for help. LOG: [ObjectDB 2 .5.1_05 ... /1107 support Support Build 2 .7. 2 _01 should fix this bug. support Support Build 2 .7. 2 _01 has a side effect that introduces another bug ( issue #2142 ). Build 2 .7. 2 _02 should be used. support Support | |
JDOQL Subqueries (JDO 2.1) Subqueries (nested queries) have been added to JDOQL (JDO Query Language) in JDO 2 .1. This is the main feature of JDO 2 .0- 2 .1- 2 . 2 that is not implemented yet in ObjectDB 2 . support Support | |
InternalException using 2.3.7_12 Sorry can't shed any light on this, other than the code where this came out of, worked fine with 2 .3.7_02. I had to upgrade to 2 .3.7_12 to pickup the fix for wildcard search on index, and now get this. [ObjectDB 2 .3.7_12] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server | |
JPA Query Criteria API (JPA 2.0) a factory. ObjectDB supports dynamic definition of JPQL queries as strings. Support of the new JPA 2 ... Query API was just added to ObjectDB in version 2 .1.1_01. It will be officially supported and documented starting version 2 . 2 , which is expected to be released later this month. support Support | |
New issues with queries using build 2.7.8; WHERE a.startStep.stepNumber = 0 AND (s.name IN ('In1') OR a.tcSignal IS NULL) With 2 .7.6_b6 we get the expected three result objects. But with 2 .8.0 we get only two result objects ... you for this report. Build 2 .8.0_01 includes a fix. support Support There is an issue with build 2 .8.0_01 | |
[ObjectDB 2.6.7_04] Unexpected exception (Error 990) Since Version 2 .6.7_04 we get the following NullPointerException at Query execution: [ObjectDB 2 .6 ... operation (before executing a query). It doesn't seem related particularly to build 2 .6.7_04 or ... working, but build 2 .6.7_05 includes some addition that maybe can help. support Support 2 .6.7_05 works | |
[ObjectDB 2.4.3_07] Unexpected exception (Error 990) [2012-10-05 13:14:18 #7 store] Database '/home/glassfish/objectdb- 2 .4.3_07/db/test.odb' is opened by 7042@edi-gui-sbr-devel [2012-10-05 13:14:18 #8 server] [ObjectDB 2 .4.3_07] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_35 (on Linux 2 .6.32-300.10.1 | |
JPA Metamodel (JPA 2.0) added to ObjectDB in version 2 .1.1_01. It will be officially supported and documented starting version 2 . 2 , which is expected to be released later this month. support Support ObjectDB version 2 . 2 .0 was just released with full support of the JPA Metamodel API , including complete test coverage and documentation . support Support | |
[ObjectDB 2.8.3_01] Unexpected exception (Error 990) Seeing strange new error, with previously working code! Objectdb: 2 .8.3_01 JVM: 1.8.0_252 OS: Ubuntu: 18.0.4 ---- [ObjectDB 2 .8.3_01] Unexpected exception (Error 990) Generated by OpenJDK 64 ... .ThreadExecutorMap$ 2 .run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable | |
[ObjectDB 2.6.0_04] Unexpected exception (Error 990) com.objectdb.jpa.JpaQuery.getResultList Hello, the following exception appears when we execute a query: [ObjectDB 2 .6.0_04 ... .renderers.swt.DirectContributionItem$ 2 .handleEvent(DirectContributionItem.java:331) at org.eclipse.swt ... build 2 .6.1_01 runs the query on the last available data, but for a complete solution we may need a test case. support Support | |
Cannot insert more than about 2^20 objects other indexes = 1048577 = 1+ 2 ^20 . Is this a coincidence? I hope this is not an ObjectDb limitation. Regards Doctor output: ObjectDB Doctor [version 2 .5. 2 _05] Copyright (c) 2013, ObjectDB | |
[ObjectDB 2.4.1] Unexpected exception (Error 990) Hi, getting this unexpected exception, would welcome advice: [ObjectDB 2 .4.1] Unexpected exception ... .ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$ 2 .evaluate(ParentRunner ... ; } } A better error message is produced by build 2 .4.1_01. support Support | |
ClassCastException after upgrade to 2.3.5_03" field is a byte[]. This worked ok in 2 .3.3_06. felixobjectdb Richard Szurgot Thank you for this report. Please try build 2 .3.5_04 that should fix this new issue. support Support | |
ObjectDB 2.5.4 Added empty implementation of new JPA 2 .1 methods. Implemented new JPA 2 .1 EntityManagerFactory methods: createEntityManager , unwrap . Improved retrieving persistent string fields by using "".intern() for empty strings. Fixed a bug in queries on composed embedded primary key ( issue #1301 ). | |
ObjectDB 2.5.6 queries. Fixed an exception ( NullPointerException ) in update queries (since 2 .5.5_12). Fixed ... queries. Fixed some bugs in converting old ObjectDB 1.x database files to ObjectDB 2 .x. Fixed a bug |