Home » Search

About YEAR

41-50 of 62Refresh
Forum
1

OptimisticLockException

Ran into this error for the first time (after many years of using odb): Caused by: com.objectdb.o._OptimisticLockException: Optimistic lock failed for object model.UserSession#28 (object has version 2 instead of 3) Also the first time I'm using odb in C/S mode rather than embedded
Forum
1

OptimisticLockException

that would be done automatically. Having used objectdb for nearly 10 years now, all in embedded mode, I'm a bit
Forum
1

PersistenceException: Failed to locate field

) {     com.objectdb.Enhancer.enhance("app.model.*"); Note: I removed programmatic many years ago
Forum
1

Pessimistic Lock Timeouts setting

, my prototype app (Stale as of july last year due to work commitments) has never seen the issue
Forum
1

Recovery file does not match db file

it and restart the database server. Version 2.3.1 is nearly one year old - you should upgrade your server
Forum
1

Remove an entity which attributes were changed - OptimisticLockException

are identical. I checked all of this with a debugger.   We had a similar issue last year 2015-11-09
Forum
1

Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations

public method." At one stage, some years ago when I was using EclipseLink, I was using the setters
Forum
1

Roadmap - no progress - any plans - transparency?

of stability and that is not something that can be taken for granted. In the first years
Forum
1

Setting temp directory location in ObjectDB

was released many years ago when Java didn't provide a standard file locking). ObjectDB 1.x is now
Issue
1

Sometimes the ObjectDB throws an internal expeption if a persist() was executed

status is active since one year. But its not an ObjectDB issue. The problem is just that we started