ObjectDB Database Search

javax.persistence.NamedQuery; import javax.persistence.Query; import javax.persistence. Version ; import ... id = "1"; @SuppressWarnings("unused") // used by JPA @ Version private int version ; @Basic protected ... javax.persistence.ManyToOne; import javax.persistence.MapsId; import javax.persistence. Version

/SystemDB.odb db/SystemDB.odb.rpmnew ObjectDB Doctor [ version 2.6.3] Copyright (c) 2015, ObjectDB Software ... fields will cause the corruption? An example would be beneficial. Also, can we assume that all version prior to 2.6.4_02 have this problem? In particular version 2.5.5_14 and 2.6.1_05? Thank you Emil

.jboss.modules] JBoss Modules version 1.0.1.GA 13:49:14,316 INFO [org.jboss.msc] JBoss MSC version 1.0.0 ... ) Deploying JDBC-compliant driver class org.h2.Driver ( version 1.2) 13:49:22,868 INFO [org.jboss.as ... service thread 1-1) JBoss Remoting version 3.2.0.Beta2 13:49:24,513 INFO [org.xnio] (MSC service thread

after upgrading to 2.9.0 (because of the other problems in former versions ), the database destroys ... the engine that manages the database storage, at least in the last 2 years, so there is nothing in version 2 ... there was a situation in which more than one process accessed the database? Again, version 2.9.0 uses exactly

; homplex@homplex01:~$ java - version java version "1.6.0_18" OpenJDK Runtime Environment (IcedTea6 1 ... + agent homplex@homplex01:~$ java -javaagent:/home/homplex/objectdb/objectdb.jar - version java version "1 ... -Dcom.sun.management.jmxremote.authenticate=fals -versionjava version "1.6.0_18" OpenJDK Runtime

Hi, I've been getting the following exception when trying to query ObjectDB in server mode version ... . The number 36 indicates type version number 36 (i.e. after 35 modification of some entity type). You have an object with that type version number but the type version doesn't exist in the database

enhanced additional getters/setters, because the additional methods now use (since about version 2-6 ... the method as a setter or getter), prior to version 2-6-5: [accessor_name]_odbHidden_ Where [accessor ... ; http://www.objectdb.com/object/db/database/ version /2-6-5     - Renamed internal

. However, the test case on that forum thread still passes with the last ObjectDB version . ObjectDB maintains a version number for every entity object, which is increased on every update. An  OptimisticLockException  is thrown when that version number indicates a concurrent update by another user (using

javax.persistence.NamedQuery; import javax.persistence.Query; import javax.persistence. Version ; import ... "; @SuppressWarnings("unused") // used by JPA @ Version private int version ; @Basic protected java.lang.Integer ... .persistence. Version ; @Entity @IdClass(CompoundKeyMapItem.CompoundKeyMapItemId.class) public class

sure the enhancement script runs the same objectdb.jar library version that the program runs with. I ... yet tried versions between objectdb-2.6.3_04 and objectdb-2.6.6_07 (bracketing to find which one broke it). But I know that I can't run any of my objectdb-based programs using a version later

that it might get corrupted because the manual says that we must not access ObjectDB with different versions ... , where the previous version of a class is used by some servers, then others come with the new version , then finally all of them get the new version ? So...basically...concurrent access with version x

.persistence.Temporal; import javax.persistence.TemporalType; import javax.persistence. Version ; public ... ; private Long version ;         private Date startDateTime;   ... (other.getId()) && version .equals(other.getVersion());         }   

. Which ObjectDB version are you using? Try the last ObjectDB version , which should fix this issue ... them again, or use an ObjectDB version before the fix, with an UPDATE queries that change the IDs ... _02 version in our test enviroment. I think we have a different issue from the one in the forum

is considered temporary. Version 3.x (currently in development) will add better support for large ... .     support Support the new version caused an unexpected exception [ObjectDB 2.8.7_05 ... .JpaQuery.getResultList(JpaQuery.java:726) btc_es BTC EmbeddedSystems the previous version 2.8.7_04

;             // Refresh the entity to ensure we have the latest version ... ;     // In case of an optimistic lock failure, get the latest version , and loop back to redo ... has version 1 instead of 2) [TestEntity:1]" For me, this is always reproducible in the example I posted

get this stack: 13:52:01,121 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA 13:52:01,304 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA 13:52:01,347 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 13:52:01,959 INFO  [org.xnio] XNIO Version 3.0.3.GA 13

:757) I checked multiple times if the versions match. They do. DB server version 2.6.2. Client version 2.6.2. Also there's only one objectdb jar on the classpath. It's also not a network problem ... if different ObjectDB versions are in use on the client and on the server, but such exceptions

the directory I created by unzipping the maven version of your tutorial. In this version eclipse won't make the jar file to copy to tomcat and I don't know why. In the version were I manually created ... 6 server icon indicating the jar has been deployed to the tomcat6 server. Neither version will run

.Transient; import javax.persistence. Version ; @MappedSuperclass public class DataObject { @Id @GeneratedValue protected int id; @ Version protected long version ; @Transient protected EntityManagerFactory emf ... " + id + " version " + version );   EntityManager em = emf.createEntityManager();   em

. support Support My old- version (2.4.7_08) After installing the new version (2.4.7_18):   1) my recent db-file, created with the old- version , has been copied to the local folder of the new version automatically 2) But I can't open the db-file with the objectDB explorer, neither with the old- version

there ODB version  2.8.3.b05 in embedded mode. java.lang.NullPointerException: Cannot invoke ... tried also the ODB doctor on that DB file, but it wrote nothing special: ObjectDB Doctor [ version 2.8 ... (class files) to a version that works well with other databases and/or switch to the last ObjectDB

.modules] JBoss Modules version 1.1.1.GA 04:56:01,336 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 04:56 ... [org.xnio] XNIO Version 3.0.3.GA 04:56:02,040 INFO [org.jboss.as.server] JBAS015888: Creating http ... Implementation Version 3.0.3.GA 04:56:02,056 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

version but it doesnt work for me. I have Windows 64bit with JAVA as you can see below. The version ... cannot be found when running server or explorer. C:\java - version java version "1.6.0_29" Java(TM) SE ... Support Just tried, the versions with underscore in name are running fine, versions

:   08:17:21,359 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 08:17:21,544 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 08:17:21,588 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting 08:17:22,209 INFO [org.xnio] XNIO Version 3.0.3.GA 08:17:22,209 INFO [org

objectdb version . We had to create new keys multiple times because of the unstable activation ... stability issues have been fixed in version 2.9.3 and there are no new known issues. If you create a new activation using version 2.9.3 or later and still have issues (except when the MAC addresses

via the toString() method). The DB Doctor finds then errors like this in the file: ObjectDB Doctor [ version ... how could this happen and how to avoid it ? jakab Gergely Jakab Since you are using version 2.8.3_05 it might be the critical schema bug ( issue #2621 ) that was fixed in version 2.8.4. Please try

to finish its task. The version of ObjectDB I am running is 2.6.1.b02 Any idea what is causing ... version . jakab Gergely Jakab Unfortunately the "Failed to read from file '/path_to_db/dbFile.odb'" error ... will be needed in order to explore this issue, including range of affected ObjectDB versions . support Support I

match the reported version (2.8.3). Please double check which version /build you use. In addition, you should also try the most recent version (2.8.8) and provide the generated stack trace using that version , if the exception is thrown. support Support Sorry the version name is wrong. Its 2.8.1

in a previous thread, this is the undesired consequence of using ObjectDB with different versions ... server is down and that only the new versions of the entity classes are in use by ... pbdmodel.impl.AktImpl has 161 versions . Generally speaking, new versions are only created by adding or

values in updated entity. There is a problem however with accessing "old" version of object stored in ... . So, is it somehow possible to implement something similar in ODB? Or is there any way to implement this in current version ... of entity update history) is expected to be added in a future version of ObjectDB. Please subscribe

conversion of id attributes, of version attributes, of relationship attributes, or of attributes

may optionally have a field or property annotated Version , which holds a value used to detect

-Georg Zwicker What version of ObjectDB are you using? Any additional information related ... .7.1_01 in our app, the doctor is the version from march 2016. Database file is around 35 GByte, how can we handle that ? hgzwicker Hans-Georg Zwicker Is it the Doctor of version 2.7.0_01? If not

and will be examined further. Repairing the database with the Doctor should hopefully keep only the new version and remove the old version with missing parts. Please run the above query on the repaired database ... users use  version -check="false" and others  version -check="true". This is probably not

the issue! It works fine now. btc_es BTC EmbeddedSystems Hello, if we use the version 2.7.4_04 ... listeners for pre persisted and post persisted in order to check the entity version number. For example a new entity is created (entity version = 0), pre persisted (entity version = 0), post persisted

it will report: Java/JVM version : 1.8 Java/JVM detail version : 1.8.0_74 ObjectDB enhancer: begin ... (Element.java:1) ... 21 more To compare with objectdb-2.6.3_04.jar Under /lib there are 2 versions ... that version during enhancement (use File view mode not Project view mode in NetBeans to find

. In the current implementation ObjectDB is embedded in the driver. Any 2.x version of the driver ... is fixed for all 2.x versions . However, since the client-server protocol is occasionally being updated, there should be a match between the ObjectDB BIRT client-server protocol version and an ObjectDB

is much more complex and could easily be inaccurate. Future version of ObjectDB will probably ... Support we implemented version 2.8.0_02, added:             ... query: ( version 2.7.6 it takes 47 ms, version 2.8.0_02 it takes 700 ms): SELECT DISTINCT o.parentNode

Zwicker The new ObjectDB version will be released today or tomorrow morning. No problem with broken references, if their existence is planned and managed by the application. support Support Version 2.7.2 includes the changes that are specified on #15 above. Please run the Doctor of the new version

environment, but now in field. Object DB version was upgraded maybe two times in the last months in ... version 2.8.4 that fixed that issue. support Support I think the schema may changed 2-5 times ... ; ... itsme Martin Petzold It is usually difficult to know the total number of schema versions

you for this report. support Support Version 2.8.8_03 should throw an exception with the correct ... whether it is also solved. support Support With version 2.8.8_03 we get another exception stack trace ... btc_es BTC EmbeddedSystems The exception in #6 is similar to #1, so apparently version 2.8.8_03

versions (2.4.7, 2.4.6). If it is a new problem, we may be able to track the change the causes it. support ... for a item thats not in the db.   Stefan Stefan Mair The problem is in version 2.4.7. I will try with an older Version on Monday. Stefan Stefan Mair The 256 observation is interesting

Dear Support Team Changing objectdb from version 2.7.4 to version 2.8.1 I found, that query against embedded objects doesn't work as expected and the formerly green UnitTest ( Version 2.7.4) turns red ( Version 2.8.1). For what I thought I realized is, that the version 2.8.1 was sensitive

we are facing massive problems with our system using the latest version of objectdb: - around 2 ... use the latest version 2.7.4_02, with versions of 2.7.3 we never had these problems ... .7.3 works well and 2.7.4_02 doesn't. Can you check version 2.7.4? Could you please provide

Hi, The problem occured since an update from my old- version (2.4.7_08) to the new version (2.4.7_18): 1) my recent db-file, created with the old- version , has been copied to the local db-folder of the new version automatically 2) But I can't open the db-file with the objectDB explorer

I switched to version 2.8.2 and now it seems that my enum types are not recognized and the field ... the interface (but different package)? itsme Martin Petzold I checked version control. The entity ... am not totally sure what is happening. The test case passes for both versions (2.7.4.b03 and 2.8.2

we update to the latest version from 2.7.6. Now we have the problem that we have numerous logs ... since version 2.7.6 that could possibly effect query execution. Could you please explain or post ... . support Support currently we have no chance to really test that with all the sub versions

we how have compiled with the 02 version and the situation is like attached hgzwicker Hans-Georg Zwicker ... ObjectDB version doesn't look related, it may be simply the exact timing in which each thread dump was  ... .properties.name = 'feedbackState' and o.properties.doubleValue 0 and p2.doubleValue  the version 03

the new implementation of temporary files for very large transactions. Version 2.6.7 should fix this bug. support Support Version 2.6.7 don't fix the bug:  (Now there are other line Numbers in PAG ... Support Also Version 2.6.7_1 don't fix the bug: Exception in thread "Thread-174" [ObjectDB 2.6.7_01

to be releasing a trial version of this product in a few weeks, at which point we will be wanting to buy ... Support New version of objectdb installed.  Will report back log entries soon. sjzlondon Steve Zara ... , and I discovered that two different versions of the objectdb.jar may have been used by different