About failure

71-80 of 114Refresh
Result
1

ObjectDB version 2.6.8

Version 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index
Issue
1

Another NPE on em.createQuery(query).getResultList()

in the test if you can't deduce the exact failure from this. This is another unrelated NPE
Issue
1

Different behavior for two equal queries

component that causes this query execution failure? Does it have navigation through null
Forum
1

em.flush(); em.clear(); loosing data and not persisting managed objects

().commit(); } } Here is my failure output. i=75 i=76 i=77 i=78 i=79 flushing i=80 Validate failed for i
Issue
1

Error 990 when querying a class with persistence-capable-superclass

me with this work? Could it be because of the superclass, as I guessed? Or a failure of run-time
Forum
1

evictAll() behavior

seems also related to a failure in using enhancement (since in reflection mode ObjectDB
Forum
1

Failing to read entities under load in multithreaded tests

and 1000 iterations I still get 1 or 2 failures. Regards, Natalia. I've also just noticed that the error
Issue
1

File lock exception on odb$

Not sure if this is an objectdb issue or not but I thought I'd raise it just in case. We had a server failure which caused an unexpected reboot. As a result, the application services which use objectdb were not shutdown properly which in turn meant we had several odb$ files left behind. I
Forum
1

How to deploy an Objectdb project with Jboss AS 7?

back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Guestbook.war
Forum
1

How to Use a SF with extended Persistence Context?

.1-8080-1) ARJUNA012127: TwoPhaseCoordinator.afterCompletion - returned failure