4 | Failed to read DB file while online backup is running could cause this. Is it a new exception? Can you check build 2.6.2 and 2.6.1 to find the last build ... . Could you please check for more details in the log? support Support You are right I just found the full stack traces in |
4 | Odb file versionHi, Do we have any mechanism to knwo whether the odb file belongs to 1.x object db or 2.x object db. Before migrating all the odb files from objectdb 1.x to 2.x, i would like to add a check if it is already migrated. Any API which is exposed to check the odb files version ? binitbhaskar Binit |
4 | EM.find() is suddenly slower eager fetch that affects the performance of further operations. Could you please check build 2.8.6_06 that tries to improve performance in such cases? If it doesn't help, please check |
4 | Visibility of changes in Transaction is not visible to a JPA QL QueryI have two simple Entities ( see attachment ) and a simple SLSB with container managed transactions which is called by a trivial servlet. Inside a UserTransaction I add a number of items then check ... JFK John Francis Please check if this is due to the default flush mode. In most JPA implementations |
4 | Performance tuning, best practices="false" sync="false" path="." mode="write" /> <locking version-check="true" /> <processing cache ... (possibly a complex query) is slow also for a single user? i.e. can you check if the performance |
4 | Adding EntityListener Throws Unexpected Internal Exception, we can easily provide a fix. Could you please check in this context the super class of your listener class ... is closed. Thank you! I checked the imports and there was a similar class having same name. I |
4 | multi thread application, id field sporadically null with the field that is declared as @Id having the value null (what is not correct, we checked ... memory, which is a new object that has no id yet. You may want to check if using a new EntityManager |
0 | again merger missing logs + objectdb exception to worry about these stack traces. To be on the safe side please use the Doctor to check the database ... Support ok, we'll check the other changes that we made hgzwicker Hans-Georg Zwicker our fault |
0 | javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName this check quickly in between other work; for previous build checks I was only working on ObjectDB |
0 | TYE NullPointerException object wasn't loaded for the check but by looking at it in the debugger a load was forced. I put a simple loop iteration in front of the check to force a load (and prove the object was not detached |
