7 | 500Mb ObjectDb database opening issue : (AppMain.java:34 thread:main): main(): Java version used:1.8.0_66x32 1/23/2016 15:38:42.3842: INFO ... completed. 1/23/2016 15:42:35.4235: INFO : (AppMain.java:34 thread:main): main(): Java version used:1.8 ... completed. 1/26/2016 20:49:23.4923: INFO : (AppMain.java:34 thread:main): main(): Java version used:1 |
7 | Wrong data stored in time only fields.persistence.TemporalType; import javax.persistence.Version; public class DateTimeTest { public ... ) public static class DateTime { private Long id; private Long version ... .equals(other.getId()) && version.equals(other.getVersion()); } public int hashCode |
7 | Wrong @Id type version are you using? Try the last ObjectDB version, which should fix this issue/ To repair IDs ... an ObjectDB version before the fix, with an UPDATE queries that change the IDs to the correct type). support Support We are using ObjectDB 2.4.6_07 in our production enviroment and 2.5.6_02 version in |
7 | problems using the explorerwe are currently evaluating objectDB. Environment OSX 10.9.2, JavaSE-1.7 Version: Kepler Service ... > <groupId>com.objectdb</groupId> <artifactId>objectdb</artifactId> <version>2.2.5</version> </dependency> ... Problem: we created a small example that just writes and retrieves |
7 | EM close causes an exception other users are expected. This mode is considered temporary. Version 3.x (currently in development ... . support Support the new version caused an unexpected exception [ObjectDB 2.8.7_05] Unexpected exception ... .java:726) btc_es BTC EmbeddedSystems the previous version 2.8.7_04 does still work as expected |
6 | How to Use a SF with extended Persistence Context?: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:52:01,960 INFO [org.jboss.as.server |
6 | Mismatch client-server protocol prefix(AbstractPlatformTransactionManager.java: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 ... the request. That check could fail if different ObjectDB versions are in use on the client and on the server |
6 | How to resolve 404 errors with Eclipse/Maven Spring MVC 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 the files following ... the jar has been deployed to the tomcat6 server. Neither version will run with tomcat 6 |
6 | newbie - lots of exeptions.preDestroy(ASURLClassLoader.java:179) and our persistence.xml file looks like <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence ... this process by specifying <exclude-unlisted-classes/> in the persistence.xml: <?xml version="1.0 |
1 | criteria api / embedded objects / where orderDear 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 |
